wangyong9999 opened a new pull request, #374:
URL: https://github.com/apache/paimon-cpp/pull/374

   ### Purpose
   
   Linked issue: N/A.
   
   Repeated scans of the same snapshot and bucket decode the manifest lists 
before checking the snapshot live-entry cache. Check that cache after selecting 
the snapshot, and bypass manifest-list reads and decoding on an exact hit. 
Misses still rebuild the complete bucket; each scan still applies its 
request-specific filters.
   
   Store the table file count with the cached entries to preserve skipped-file 
metrics. An exact hit now reports zero scanned manifests. This targets repeated 
point-read planning without introducing another cache or changing snapshot 
discovery.
   
   ### Tests
   
   - Local C++17 Release build of the identical patch on the downstream main 
branch succeeded without compiler warnings.
   - 88 focused scan, snapshot, predicate, serialization, and bucket-pruning 
tests passed on that downstream build. Regression coverage checks no 
manifest-cache access on an exact hit, changed predicates, eviction/rebuild, 
and retained file counts; existing tests cover snapshot changes.
   - `pre-commit run --all-files` and `git diff --check` passed on this 
upstream checkout.
   - Upstream CMake/CI validation is pending. No throughput improvement is 
claimed yet; runtime comparison is in progress.
   
   ### API and Format
   
   No public API, table storage format, or protocol change. Only the transient 
serialized snapshot-cache payload changes; its magic is versioned so old cache 
entries fall back to rebuilding. Snapshot selection and cache eligibility 
remain unchanged.
   
   ### Documentation
   
   Updated the manifest-entry cache guide to describe bypassing manifest lists 
and exact-hit scan metrics.
   
   ### Generative AI tooling
   
   Generated-by: Codex based on GPT-6.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to