[Enhancement] Enhance KVRecord

[superhx]

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

[yyyCode]

I couldn't find KVRecord in the AutoMQ source code, is it part of AutoMQ or its dependencies?

[AminMortezaie]

Hi team 👋,

I’d like to take this on if it's still unassigned.

I’ll investigate the reassignment path and ensure it gracefully handles the case where a partition has no segments (e.g., by skipping or initializing default state).

I’ll also add a test to cover this edge case. Let me know if there are any preferred conventions or context I should keep in mind!

Best,
Amin

[AminMortezaie]

I've added my merge request.

[1sonofqiu]

@AminMortezaie Thanks for your contribution! I'll take a look at it within a few days.