modelix / modelix/modelix.core
split very long operations lists to limit the maximum size of a KV entry
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 16
- Forks
- 10
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 26
Description
The class CPOperationsList stores all the operations that were applied to a version. If there are lots of changes this list can become long and the entry stored on the model-server becomes big. This might be a problem that can be avoided by splitting a long list into a tree like data structure.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with model-client/src/commonMain/kotlin/org/modelix/model/persistent/CPOperationsList.kt and trace how it stores operations applied to a version. Define how a long list should be represented as a tree and how the model-server stores each entry. Done means very long operation lists are split so no single KV entry becomes excessively large.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100