otto-de / otto-de/api-guidelines
[new rule] compacted topics must always be ordered
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 50
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
(i) This issue has been manually transferred from a former internal repository, as a private repository issue cannot be transferred to a public repository.
Context
If a compacted topic is used, it must always be ordered so that the last written data event is the most current for a used key. If a situation might occur in which the last written data event is not the most current for the specified key, the compaction process will delete the most current event.
Contributor guide
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
No file, test, or entry point is named. First locate the existing guidance for compacted topics in this repository and review how rules are documented; done means the intended ordering rule and its data-loss condition are documented unambiguously.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100