Skip to content

persistency: Feature request for KVS #219

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

LittleHuba
Copy link
Contributor

No description provided.

@LittleHuba LittleHuba force-pushed the ulhu_persistency_kvs branch from 40d9329 to 27f70a2 Compare January 24, 2025 17:09
@LittleHuba LittleHuba force-pushed the ulhu_persistency_kvs branch from 27f70a2 to bbaf461 Compare January 24, 2025 17:10
@LittleHuba LittleHuba changed the title persistency: Draft Feature request for KVS persistency: Feature request for KVS Jan 24, 2025
@qor-lb qor-lb linked an issue Jan 28, 2025 that may be closed by this pull request
- Supported Datatypes: Primitive Datatypes & Non-Primitive Datatypes; To be coordinated with IPC/Communication CTF, to use the same datatypes
- Tooling to modify/access content of KVS "from the outside"
- KVS should store default values
- Integrity of the KVS should be checked
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional points:

  • Snapshot feature of KVS to recover previous state, e.g. for failing integrity checks

Update of draft document
Copy link

The created documentation from the pull request is available at: docu-html

@guysagnes guysagnes moved this to In Progress in Feature Requests Apr 17, 2025
@guysagnes guysagnes self-assigned this Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

Feature Request for Persistency
4 participants