Skip to content

feat: Add methods to wait for consistency with a token#2762

Merged
jinseopkim0 merged 6 commits intomainfrom
consistency-token
Feb 6, 2026
Merged

feat: Add methods to wait for consistency with a token#2762
jinseopkim0 merged 6 commits intomainfrom
consistency-token

Conversation

@jinseopkim0
Copy link
Copy Markdown
Contributor

This change adds support for checking consistency using a provided token, enabling distributed workflows. It also adds convenience methods to BigtableTableAdminClient for generating and waiting for a token automatically.

This addresses the Consistency Tokens CUJ.

Tracking Bug: b/475820272

This change adds support for checking consistency using a provided token, enabling distributed workflows. It also adds convenience methods to BigtableTableAdminClient for generating and waiting for a token automatically.

This addresses the Consistency Tokens CUJ.

Tracking Bug: b/475820272
@product-auto-label product-auto-label bot added size: m Pull request size is medium. api: bigtable Issues related to the googleapis/java-bigtable API. labels Jan 26, 2026
@jinseopkim0 jinseopkim0 marked this pull request as ready for review January 28, 2026 17:20
@jinseopkim0 jinseopkim0 requested review from a team and lqiu96 January 28, 2026 17:20
* Polls an existing consistency token until replication is consistent. Useful for checking
* consistency of a token generated in a separate process. Blocks until completion.
*
* @param tableId The table to check.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

qq, I'm assuming this means the downstream table? e.g. If A wants to replicate data to B, then tableId refers to B?

If so, does that mean that replication is limited to one table or that a user would need to call this method multiple times?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This method is not replicating table A to table B, it's about replicating table A across all clusters (same as awaitReplication method). The user would need to call once per table. Please let me know if you still have questions.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh gotcha. I think would make more sense to a bigtable customer (table replication across the cluster).

@jinseopkim0 jinseopkim0 requested a review from a team as a code owner February 5, 2026 20:22
@jinseopkim0 jinseopkim0 requested a review from lqiu96 February 5, 2026 20:24
@jinseopkim0 jinseopkim0 requested a review from lqiu96 February 5, 2026 22:54
@jinseopkim0 jinseopkim0 merged commit b4a90b2 into main Feb 6, 2026
28 checks passed
@jinseopkim0 jinseopkim0 deleted the consistency-token branch February 6, 2026 00:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigtable Issues related to the googleapis/java-bigtable API. size: m Pull request size is medium.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants