Versions Compared

Old Version 21

changes.mady.by.user Unknown User (jolshan)

Saved on

compared with

New Version 22

changes.mady.by.user Unknown User (jolshan)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

No argument behavior on the storage and upgrade tools is to set all the features to the latest stable version.

For both tools:

  • Add version-mapping command to to look up the corresponding features for a given metadata version. Using the command with no  --release-version  argument will return the mapping for the latest stable metadata version.
  • Add dependencies command to look up dependencies for a given feature version supplied by --feature flag. If the feature is not known or the version not yet defined, throw an error. 
     

...

Code Block
bin/kafka-storage.sh version-mapping // Returns latest stable version mapping
> Feature versions for metadata.version=19 (3.7-IV4): 
> transaction.protocol.version=2
>, group.coordinator.version=1

bin/kafka-storage.sh version-mapping --release-version 3.6-IV1
> Feature versions for metadata.version=13 (3.6-IV1): 
> transaction.protocol.version=0
>, group.coordinator.version=0
 
bin/kafka-storage.sh version-mapping --release-version 2.9-IV2 // throws error, not a valid version

bin/kafka-features.sh version-mapping
bin/kafka-features.sh version-mapping --release-version 3.6-IV1

kafka-feature dependencies --feature transaction.protocol.version=2
> transaction.protocol.verison=2 requires metadata.version=4 (listing any other version dependencies)

kafka-feature dependencies --feature metadata.version=17
> metadata.version=17 has no dependencies

...