Styxis
Company
Knowledge

Spanner change streams: an RPC end is different from restriction completion

Distinguish an artificial end of one RPC from completion of the whole restriction.

The range left after one query

Distinguish an artificial end of one RPC from completion of the whole restriction. Explain tracker progress against the boundary actually read. Keep the two ends separate in the table supplied to Truthound; claiming the full end without read evidence can cause the next run to skip source data. [1, 2, 3]

Report evidence and release evidence

Beam #39821 describes a Spanner change-stream tracker potentially advancing from a calculated artificial query end to the original, possibly unbounded restriction end. The author links PR #37326 as the fix. The short report does not quantify customer loss or CPU-dependent failure rates, and this article does not establish which deployed release carries that change. [1]

Place three boundaries together

Show the query end, verified read boundary and stored tracker position together. Hold resume approval when an unread interval was marked complete. Match partition and boundary-inclusion rules, preserve read evidence per RPC and include keys just after the boundary in the resume test. [1, 3]

A ledger confirming through 40

The illustrative full range is tick 0~100 and one RPC ends at 40. Independent evidence confirms processing only through 40, so the approved completed boundary is 40. Observed 40 meets this condition; a tracker claim of 100 fails. Do not infer the actual system’s timestamp unit or inclusion rules from these logical ticks. [1, 3]

Give progress values a meaning

Truthound Core Python SDK 3.3.2 can compare prepared verified_processed_end and claimed_processed_end using ColumnPairValidator with relationship="==". The operator supplies non-missing values with the same boundary meaning. The SDK does not repair the Spanner RPC or restriction tracker, or restore changes never read. [1, 2, 3]

When to declare full completion

Confirm the exact Beam version carrying the change and reconcile source keys at the same boundary. If evidence actually confirms processing through 100, the fixture’s 40 is not a universal cap. Declare a full restriction complete only after checking its full processing evidence and resume contract. [1, 3]

Application conditions

Match partition and boundary rules, and retain the artificial query end separately from the original restriction end.

Alternatives

Confirm the version carrying the linked correction and test source keys immediately after the boundary.

Limitations

  • The SDK does not repair RPCs or trackers; the report does not quantify CPU-dependent loss.

Evidence

Event checked
Subject checked
Modified