[
https://issues.apache.org/jira/browse/KAFKA-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551873#comment-16551873
]
Matthias J. Sax commented on KAFKA-7175:
----------------------------------------
We could maintain a map from Kafka version to metadata version in the python
code. Each time we change the metadata version we would need to update this map
in Python code manually. But this happens max once per release and thus should
be ok to do manually IMHO.
> Make version checking logic more flexible in streams_upgrade_test.py
> --------------------------------------------------------------------
>
> Key: KAFKA-7175
> URL: https://issues.apache.org/jira/browse/KAFKA-7175
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ted Yu
> Priority: Major
>
> During debugging of system test failure for KAFKA-5037, it was re-discovered
> that the version numbers inside version probing related messages are hard
> coded in streams_upgrade_test.py
> This is in-flexible.
> We should correlate latest version from Java class with the expected version
> numbers.
> Matthias made the following suggestion:
> We should also make this more generic and test upgrades from 3 -> 4, 3 -> 5
> and 4 -> 5. The current code does only go from latest version to future
> version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
