Skip to main content

Module error

Module error 

Source
Expand description

Error taxonomy and per-stage error policies.

Three classes of failure exist in a pipeline (see docs/DESIGN.md): retryable (transient I/O — handled by the sink retry layer), record-level (a bad payload or failed user code — subject to ErrorPolicy), and fatal (invariant violations — the pipeline stops). Record-level policies are deliberately limited to Skip and Fail; every skip is surfaced through metrics.

Structs§

FatalError
An unrecoverable pipeline failure: an invariant was violated or a Fail-policy stage tripped. The pipeline transitions to Failed, the partition watermarks stop advancing, and the process exits non-zero.

Enums§

DeserError
A payload could not be deserialized.
ErrorClass
Broad classification used in metrics labels (error_type) and by the retry layer.
ErrorPolicy
What to do when a record fails in a stage.
SinkError
A sink failed to write a batch.
SourceError
A source failed to poll, commit, or manage its assignment.