Skip to main content

Module checkpoint_manifest

Module checkpoint_manifest 

Source
Expand description

Unified checkpoint manifest types Unified checkpoint manifest types.

The CheckpointManifest is the single source of truth for checkpoint state, replacing the previously separate PipelineCheckpoint, DagCheckpointSnapshot, and CheckpointMetadata types. One manifest captures ALL state at a point in time: source offsets, sink epochs, operator state, WAL positions, and watermarks.

§Manifest Format

Manifests are serialized as JSON for human readability and debuggability. Large operator state (binary blobs) is stored in a separate state.bin file referenced by the manifest.

§Connector Checkpoint

The ConnectorCheckpoint type provides a connector-agnostic offset container that supports all connector types (Kafka partitions, PostgreSQL LSNs, MySQL GTIDs) through string key-value pairs.

Structs§

CheckpointManifest
A point-in-time snapshot of all pipeline state.
ConnectorCheckpoint
Connector-agnostic offset container.
InFlightRecord
In-flight data record from an unaligned checkpoint.
ManifestValidationError
Errors found during manifest validation.
OperatorCheckpoint
Serialized operator state stored in the manifest.

Enums§

SinkCommitStatus
Per-sink commit status tracked during the checkpoint commit phase.