Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeyValueStore: Method to check key-value store record exists #507

Closed
drobnikj opened this issue Feb 7, 2024 · 0 comments · Fixed by #510
Closed

KeyValueStore: Method to check key-value store record exists #507

drobnikj opened this issue Feb 7, 2024 · 0 comments · Fixed by #510
Assignees
Labels
backend Issues related to the platform backend. low priority Low priority issues to be done eventually. product roadmap Issues contributing to product roadmap. t-platform Issues with this label are in the ownership of the platform team. t-tooling Issues with this label are in the ownership of the tooling team. validated Issues that are resolved and their solutions fulfill the acceptance criteria.

Comments

@drobnikj
Copy link
Member

drobnikj commented Feb 7, 2024

It is impossible to check if a key-value record exists, and users use kvs.getRecord instead, which is inefficient.

The implementation is simple: to check if a record exists, you can use an HTTP request with the method HEAD get Record API URL.

Method:
keyValueStoreClient.exists(key: string): boolean
which returns true or false based on the record.

@drobnikj drobnikj added t-platform Issues with this label are in the ownership of the platform team. t-tooling Issues with this label are in the ownership of the tooling team. labels Feb 7, 2024
@barjin barjin self-assigned this Feb 12, 2024
@fnesveda fnesveda added low priority Low priority issues to be done eventually. backend Issues related to the platform backend. product roadmap Issues contributing to product roadmap. labels Feb 13, 2024
barjin added a commit that referenced this issue Feb 13, 2024
@drobnikj drobnikj added the validated Issues that are resolved and their solutions fulfill the acceptance criteria. label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Issues related to the platform backend. low priority Low priority issues to be done eventually. product roadmap Issues contributing to product roadmap. t-platform Issues with this label are in the ownership of the platform team. t-tooling Issues with this label are in the ownership of the tooling team. validated Issues that are resolved and their solutions fulfill the acceptance criteria.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants