You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/07/17 23:36:00 UTC
[jira] [Created] (KAFKA-7175) Make version checking logic more
flexible in streams_upgrade_test.py
Ted Yu created KAFKA-7175:
-----------------------------
Summary: 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
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)