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 f019e5d
Browse filesBrowse the repository at this point in the historyBrowse files
### What problem does this PR solve?
Issue Number: None
Related PR: #65496
Problem Summary: A condition-cache MISS allocated an extra guard bit that was published as if it
covered real rows. A later plan could therefore interpret the false guard as proof that the next
real granule had no matches. In addition, legacy and V2 scanners shared external cache keys even
though only V2 understands the persisted bitmap base. Track the authoritative granule count and
trim allocation-only guards before publication, and version V2 external cache keys to isolate the
base-aware coordinate protocol from legacy entries.
### Release note
Fix condition-cache filtering across changed metadata-pruning plans and mixed scanner modes.
### Check List (For Author)
- Test: Unit Test
- `ParquetScanConditionCacheTest.*`
- `TableReaderTest.ConditionCacheMissPublishesBitmapAfterReaderEof`
- `TableReaderTest.ConditionCacheMissIsDroppedWhenReaderClosesBeforeEof`
- `NewOrcReaderTest.ConditionCacheMissMarksSurvivingGranules`
- `NewOrcReaderTest.ConditionCacheHitUsesSplitBaseGranule`
- Behavior changed: Yes. Guard bits are not published as authoritative cache coverage, and V2
external condition-cache entries cannot be consumed by legacy scanners.
- Does this need documentation: No
0 commit comments