Styxis
Company
Knowledge

Check Delta checkpoint actions even when Parquet parses

A readable Parquet file can still be the output of a failed checkpoint write. Check actual protocol and metaData actions against the source log range before approving the candidate.

Readable can still be incomplete

File-format validity and checkpoint completeness are different contracts. A readable Parquet file may still omit the actions required to reconstruct a table. Truthound Core can inspect an operator-prepared action inventory before accepting a checkpoint candidate. [1, 2, 3]

A partial checkpoint after close

Delta Kernel issue #7174 reports 4.3.0 leaving a valid partial Parquet checkpoint when an earlier log read fails and close still runs. Protocol and Metadata actions can be missing. A follow-up proposes abort handling; it is not evidence that a deployed correction was verified here. [1]

Keep generation status

Record checkpoint-generation status, source log range, action counts, and versions. Separate mid-read failure artifacts from completed candidates. Check actual non-null actions instead of merely verifying that columns named protocol and metaData exist. [1, 3]

AddFile counts cannot replace actions

Declare the illustrative required action set as metaData|protocol. Observing both actual action kinds passes that presence condition. An empty required set fails even if many AddFile rows exist and a Parquet reader opens the file. Other checkpoint validity rules remain separate. [1, 3]

Inspect an extracted action summary

RowLevelValidator in Truthound Core Python SDK 3.3.2 can apply a supplied Python predicate to an extracted checkpoint action summary. The operator defines required actions and parses the file. The SDK does not replay Delta logs or automatically remove partial checkpoints. [1, 2, 3]

Preserve the source log

Preserve the original log while using a supported checkpoint-regeneration procedure. Verify the regenerated file, action inventory, and subsequent table load individually instead of equating a successful close with recovery. [1, 3]

Limit the failed artifact’s authority

Treat a failed producer and a readable artifact as compatible observations. The artifact is useful diagnostic evidence but should not become the authoritative checkpoint merely because its container format is intact. [1, 3]

Application conditions

Extract actual non-null action kinds and checkpoint-generation status.

Alternatives

Preserve source logs and verify file, actions, and load after supported regeneration.

Limitations

  • Do not approve checkpoint completeness from valid Parquet or action column names alone.

Evidence

Event checked
Subject checked
Modified