Skip to content
This repository has been archived by the owner on Mar 22, 2023. It is now read-only.

Exists operation #20

Closed
RobDickinson opened this issue Jan 23, 2017 · 2 comments
Closed

Exists operation #20

RobDickinson opened this issue Jan 23, 2017 · 2 comments
Assignees
@RobDickinson
Labels
API change Type: Feature
Milestone
2018

Comments

@RobDickinson
Copy link
Member

Currently this is done by doing a get where the value is ignored, but this has the overhead of copying the value string. This could be done by having a specific operation that just works against the keys. This could be done by a bloom filter (which would be KeyMayExist) or by checking the inner/leaf nodes (which would be KeyExists).
@RobDickinson RobDickinson added this to the Alpha milestone Jan 23, 2017
@RobDickinson RobDickinson self-assigned this Jan 23, 2017
@RobDickinson RobDickinson removed this from the Alpha milestone Apr 28, 2017
@RobDickinson RobDickinson removed their assignment Apr 28, 2017
@RobDickinson RobDickinson added this to the 2018 milestone Mar 22, 2018
@RobDickinson RobDickinson changed the title KeyExists (or KeyMayExist) operation Exists operation Jun 21, 2018
@RobDickinson
Copy link
Member Author

This would be helpful for JNI & FFI since no callbacks would have to be created & passed. All existing engines have an internal search method that would make this an easy implementation.

@RobDickinson RobDickinson self-assigned this Jun 21, 2018
@RobDickinson
Copy link
Member Author

Closing, will include this change in #27

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@RobDickinson RobDickinson

Labels
API change Type: Feature
Projects
None yet
Milestone
2018
Development

No branches or pull requests
1 participant
@RobDickinson