Class StepsJobPlan
java.lang.Object
com.kingsrook.qqq.backend.core.jobs.plans.StepsJobPlan
- All Implemented Interfaces:
JobPlan
The STEPS plan (and ATOMIC): run any process's backend steps from its launch
point onward, as one chunk, with frontend steps skipped (their values were
collected before launch).
STEPS: after every backend step the process values are checkpointed (fenced)
to jobs_chunk.checkpointJson, and the cooperative check runs. A reclaimed
chunk resumes after the last finished step - so a three-step process killed
after step 2 resumes at step 3 with step 2's values. Whether a step that was
running when its pod died may rerun is the job's idempotency (the reaper sends
NONE to NEEDS_REVIEW).
ATOMIC: no checkpoints; a reclaim reruns the process from the start (all or
nothing - the process's own transaction rolls back on a crash).
-
Field Summary
Fields -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionplanChunks(QRecord job) One chunk.static Map<String, Serializable> readValues(String paramsJson) The job's parameter values (JSON object), or an empty map.runChunk(ChunkContext context) Run one chunk, as the job's user.
-
Field Details
-
SOURCE_START_AFTER_STEP
- See Also:
-
-
Constructor Details
-
StepsJobPlan
public StepsJobPlan()
-
-
Method Details
-
planChunks
One chunk.- Specified by:
planChunksin interfaceJobPlan
-
runChunk
Description copied from interface:JobPlanRun one chunk, as the job's user. Call context.checkpoint and context.check at safe points. -
readValues
The job's parameter values (JSON object), or an empty map.- Throws:
QException
-