mirror of
https://github.com/kvcache-ai/AgentENV.git
synced 2026-11-05 01:17:36 +00:00
[PR #85] [MERGED] feat(overlaybd): introduce index() and flatten_with_args() from LSMTFile #168
Labels
No labels
bug
documentation
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kvcache-ai/AgentENV#168
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/kvcache-ai/AgentENV/pull/85
Author: @huang-jl
Created: 7/30/2026
Status: ✅ Merged
Merged: 7/31/2026
Merged by: @yingdi-shan
Base:
main← Head:hjl/expose-index-from-LSMTFile📝 Commits (1)
5c112bffeat(overlaybd): introduce index() and flatten_with_args() from LSMTFile📊 Changes
1 file changed (+9 additions, -2 deletions)
View changed files
📝
storage/overlaybd/src/lsmt/file/readwrite.rs(+9 -2)📄 Description
What
Expose two new capabilities from the read-write LSMTFile:
The existing flatten() method remains backward-compatible and delegates to flatten_with_args() with default arguments.
Why
Higher-level callers need access to the combined LSMT index and finer control over flatten operations, including the destination writer, UUID metadata, user tags, and write concurrency.
Previously, these capabilities were only available internally.
Design and behavior changes
index() clones and returns the internal Arc<RwLock>. Callers share the same index instance with LSMTFile and must use the existing lock for synchronization.
flatten_with_args():
The existing method now delegates as follows:
flatten_with_args(CommitArgs::new(dest_file)).Existing callers therefore retain the same default metadata and sequential write behavior. Read and write failures continue to propagate from compact_to().
Compatibility and operations
Checklist
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.