eclipse-score / eclipse-score/persistency

Add compile-time configuration for maximum Key-Value Storage (KVS) size

Open
#161 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
2
Forks
28
Avg merge
2d 16h
Merged PRs (30d)
32

Description

**Description**

The current Key-Value Storage (KVS) implementation does not provide a mechanism to define or restrict the maximum total storage size at compile time.
This capability is necessary to ensure that persistent storage usage remains predictable and compliant with the memory constraints.

**Requirement Reference**

“The Key-Value-Storage shall support specification of its maximum size at compile time.”
https://eclipse-score.github.io/score/main/features/persistency/kvs/requirements/index.html

**Current Behavior**

-The maximum storage size is not enforced or configurable at compile time.
-There is no compile-time verification or enforcement of maximum storage size, which can lead to unpredictable memory use.

**Expected Behavior**

-The maximum KVS size should be defined and validated at compile time.
-KVS shall prevent further writes once the compile-time limit is reached, returning an appropriate error code

**Implementation Summary**

A compile-time configuration option has been implemented (in cpp) to fulfill the requirement and we would like to share it with you for review.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.