Uses of Package
com.kingsrook.qqq.backend.core.jobs.plans
Packages that use com.kingsrook.qqq.backend.core.jobs.plans
Package
Description
-
Classes in com.kingsrook.qqq.backend.core.jobs.plans used by com.kingsrook.qqq.backend.core.jobs.plansClassDescriptionWhat a running chunk can see and do: its job and chunk rows, its lease, the fenced checkpoint write, and the cooperative check (pause, cancel, drain, lost lease) that plans call at safe points - between pages or steps.What a durable job chunk hands to the process steps it runs, on the thread that runs them: - a provided transaction: StreamedETLExecuteStep loads into it instead of opening (and committing) its own, so the chunk's rows and its DONE mark commit together (SAME_TRANSACTION: exactly once); - a row-error sink: transform and load steps report each failed row (file row number or record key, field, code, message) so the job can record them in jobs_row_error.Which job chunk this scope runs: the parts of an effect's idempotency key, and the process whose effect declarations apply.The chunk's cooperative check (pause, cancel, drain, lost lease), run between pages; it throws JobInterruptedException to stop the chunk.One failed row.Thrown from a cooperative check to stop a chunk at a safe point: the job was paused or cancelled, this pod is draining, or the lease was lost.Why the chunk stopped.How a job's work is split into chunks and how one chunk runs.
-
Classes in com.kingsrook.qqq.backend.core.jobs.plans used by com.kingsrook.qqq.backend.core.jobs.progressClassDescriptionWhat a running chunk can see and do: its job and chunk rows, its lease, the fenced checkpoint write, and the cooperative check (pause, cancel, drain, lost lease) that plans call at safe points - between pages or steps.