hybrid: added system.hybrid_watermarks to inspect the Hybrid table watermarks#1789
hybrid: added system.hybrid_watermarks to inspect the Hybrid table watermarks#1789mkmkme wants to merge 3 commits into
Conversation
|
|
||
| ## Scope | ||
|
|
||
| Covers Hybrid tables visible to `getTablesIterator()` plus session-local temporary Hybrid tables — the same set that appears in `system.tables`. Temporary tables are emitted with `database = ''`, matching the `system.tables` convention. |
There was a problem hiding this comment.
Covers Hybrid tables visible to
getTablesIterator()plus session-local temporary Hybrid tables
does this really need to be in the user facing documentation?
| continue; | ||
| } | ||
|
|
||
| /// Row contract case 1: N healthy rows, sorted by name for reference-file stability. |
There was a problem hiding this comment.
Do we really need to sort it? wouldn't it make more sense to let the user do the sorting?
Verification: PR #1789PR-added test — all GREEN
The new CI overview (head commit)
PR test-workflow failure
Regression-workflow failures (chronic baseline on
|
| Suite | Fails |
|---|---|
| Swarms (Aarch64 + Release) | 456 |
| Parquet (Aarch64 + Release) | 36 |
S3Export part (Aarch64 + Release) |
28 |
Same fingerprint as sibling antalya-26.3 PRs (1788, 1782, 1776, 1783, 1775, …). S3Export partition was actually green on this run. No new failure modes.
Caveat — partial frontport
PR lands on antalya-26.3 while companion features from antalya-26.1 are still being frontported in parallel. Final re-verify recommended once the rest of the bundle lands.
Verdict
Safe to merge.
Audit: PR #1789 — hybrid: added
|
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Added
system.hybrid_watermarksto introspect the hybrid tables watermarksDocumentation entry for user-facing changes
...
CI/CD Options
Exclude tests:
Regression jobs to run: