Repository navigation
collections: reuse captured physical leaf workspace on native reads - #5188
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
PR #5187 landed as 7c24acb after frozen 695f6d integrated exact e23a723. Main has the byte-identical e23a723 source tree already present in 695f6d. This ancestry merge therefore retains the existing c54bd7b tree. Preserve in-flight 695f6d local qualification; hosted CI certifies final head. No production, test, policy or inventory changes.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Ordinary native collection updates and index traversal currently rebuild physical leaf decoding state for reads already owned by a retained COW capture. Reuse the existing admitted physical-reader workspace through an optional leaf-reader capability, copying decoded bytes into the caller’s admitted destination while retaining snapshot identity, checksum/codec/inspection, capacity, fallback and Close rules.
The reader change is four paths on main and adds no owner, pool, cache, format or protocol. It includes no document-vector feature, kind105 or DATA retirement changes. Final
67aee9eincludes merged CI repair #5187 and one discovery-inventory refresh. Its four reader postimages remain identical to48bec; its complete tree is identical to locally tested695f6d.Fresh main03 and reader48bec binaries ran all five existing public32-document UpdateBatch+Checkpoint cells once at8x/count1:
These single pairs are directional, with the adverse BSON/multikey time retained. Each operation includes the original checkpoint; original activation, logical sequence, exact documents/index owners and final-zero COW resources passed. Public UpdateBatch reaches the changed physical readLeaf path through touchNativeRow after checkpoint; public Get alone uses an existing shortcut. Earlier donor document-vector measurements are not evidence for this delivery.
On695f6d, seven existing public JSON/BSON/multikey/template/retained-update/compound/owned-fetch controls passed (20 subtests, no skips). The original five reader controls and public scalar range lifecycle passed previously at production-equivalent48bec (six tops/seven subtests). Ten changed-risk race controls passed on695f6d (21 subtests, no skips). Full owning collections passed on
695f6d: 3,633 tests plus two fuzz seed groups, 2,746 subtests, ten separate skips and zero failures (529 seconds). Final67aee9e has the identical complete tree; executed-head identity is retained, with no local rerun. The remaining latest-head hosted checks are running; automatic Codex review of final67aee9eis clean, with zero review threads. The CI predecessor has landed and exact final-base ancestry is recorded by root. The future14 document-vector controls, broader Q and final-engine targets remain open.Independent exact-source review accepted the four-path change; lifetime, caller-buffer aliasing, admission, codec/CRC and fallback coverage were reviewed. Automatic Codex review of exact final
67aee9ecompleted cleanly (review); no manual review request was needed. One hosted balanced-profile build stopped before benchmark execution on a Go dependency-proxy HTTP/2 download error. Its original log is preserved. One bounded failed-job refresh was spent on that transport failure; attempt 2 passed, and the other green jobs were retained. Remaining latest-head CI is still required before merge.Reproduce the existing public benchmark with the pinned Go1.26.9 toolchain:
Fixes #5181. Broader document-vector work remains #5171; full engine and Dgraph outcome gates remain #5139/#5145/#4879.
Summary by CodeRabbit
New Features
Reliability