You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b377f17
Browse filesBrowse the repository at this point in the historyBrowse files
[fix](cloud) Refresh row-binlog partitions from MetaService
### What problem does this PR solve?
Issue Number: None
Related PR: #67181
Problem Summary: A cloud row-binlog scan can begin immediately after waiting for its target transaction to become visible. Empty-partition pruning could still use an older cached initial version and remove a partition that already contains newly visible binlog data. The previous implementation placed cloud incremental-read details directly in PruneEmptyPartition.
Keep PruneEmptyPartition generic and limit the behavior change to RowBinlogTableWrapper. In cloud mode, a row-binlog wrapper without fixed visible versions refreshes only cached-empty or unknown partitions directly from MetaService before pruning. Cached-known-non-empty partitions still avoid the RPC. Wrappers with fixed visible versions and the OlapTableWrapper base behavior continue to delegate to the origin table unchanged. The existing CloudPartition selection path also retains its previous behavior and ordering.
### Release note
Fix cloud incremental reads that could miss newly visible data because stale partition-version cache entries caused premature empty-partition pruning.
### Check List (For Author)
- Test: Unit Test
- OlapTableWrapperTest
- PruneEmptyPartitionTest
- Behavior changed: Yes. Only cloud row-binlog scans without fixed visible versions refresh cached-empty or unknown partitions before pruning.
- Does this need documentation: No
0 commit comments