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

[Enhancement] Enhance KVRecord #2343

Open
superhx opened this issue Mar 12, 2025 · 0 comments
Open

[Enhancement] Enhance KVRecord #2343

superhx opened this issue Mar 12, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@superhx
Copy link
Collaborator

superhx commented Mar 12, 2025

Who is this for and what problem do they have today?

AutoMQ team

Why is solving this problem impactful?

Currently, the following types of data are stored in the KVRecord:

  • Partition -> MetaStreamId: kafka$clusterId/$topicName/$partitionIndex -> $metaStreamId
  • Node -> NodeMetadata: __automq_node/$nodeId -> $nodeMetadata.

KVs of different functions are isolated by the prefix of the key.

Expectations:

  • Add namespace to KVRecord to more elegantly isolate (future) KVs used by different functions.
  • Add epoch to KVRecord to avoid concurrent operations of PutKVRequest accidentally overwriting KVs.

Additional notes

@superhx superhx added the enhancement New feature or request label Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant