KV Engine: Recursively list keys
**Is your feature request related to a problem? Please describe.** With a KV engine, if I want to list all keys in the directory `/foo/`, it only returns keys directly under `/foo/` For example, if I have the following keys: ``` /foo/some_key /foo/bar/some_other_key ``` A LIST operation on `/foo/` returns `some_key` and `bar/`, while I would like to have `some_key` and `bar/some_other_key` **Describe the solution you'd like** Add a parameter to either recursively return ALL keys in the provided path. **Describe alternatives you've considered** Another way to do it would be to add a parameter specifying the depth up to which look recursively for keys.
Posted by vfauth on Sep 5, 2018, 3:03 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
KV Engine: Recursively list keys
**Is your feature request related to a problem? Please describe.** With a KV engine, if I want to list all keys in the directory `/foo/`, it only returns keys directly under `/foo/` For example, if I have the following keys: ``` /foo/some_key /foo/bar/some_other_key ``` A LIST operation on `/foo/` returns `some_key` and `bar/`, while I would like to have `some_key` and `bar/some_other_key` **Describe the solution you'd like** Add a parameter to either recursively return ALL keys in the provided path. **Describe alternatives you've considered** Another way to do it would be to add a parameter specifying the depth up to which look recursively for keys.
Comments (0)
No comments yet. Start the discussion.