[Verse 1]
In the metadata world of KRaft design
Eight record types keep everything in line
Topic and Partition records hold the state
Partition Change records when we need to update
Register Broker when a new node comes online
Broker Registration Change to redefine
[Chorus]
Records and versions, keeping data flowing
API negotiation, compatibility showing
Forward and backward, rolling upgrades clean
Metadata versioning, the smoothest you've seen
T-P-P, R-B-B, A-C-E, C-F complete
Eight types of records make the system sweet
[Verse 2]
Access Control Entry manages who can play
Config Records store the settings for the day
Feature Level Records track what's supported now
API Version handshake shows the system how
When clients connect they negotiate the way
Older versions work, newer features display
[Chorus]
Records and versions, keeping data flowing
API negotiation, compatibility showing
Forward and backward, rolling upgrades clean
Metadata versioning, the smoothest you've seen
T-P-P, R-B-B, A-C-E, C-F complete
Eight types of records make the system sweet
[Bridge]
Rolling upgrades happen node by node
Different versions but they share one home
Forward compatibility means newer reads old
Backward compatibility, the story's retold
Graceful degradation when features don't align
Version negotiation keeps everything fine
[Chorus]
Records and versions, keeping data flowing
API negotiation, compatibility showing
Forward and backward, rolling upgrades clean
Metadata versioning, the smoothest you've seen
T-P-P, R-B-B, A-C-E, C-F complete
Eight types of records make the system sweet
[Outro]
From Topic Records to Feature Levels high
Metadata versioning keeps the cluster synchronized
KRaft evolution with compatibility's grace
Eight record types in their perfect place