[ https://issues.apache.org/jira/browse/KAFKA-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574181#comment-16574181 ]
Ted Yu edited comment on KAFKA-7175 at 9/16/18 6:15 PM: -------------------------------------------------------- Thanks for taking this, Ray . was (Author: yuzhih...@gmail.com): Thanks for taking this, Ray. > 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 > Components: streams, system tests > Reporter: Ted Yu > Assignee: Ray Chiang > Priority: Major > Labels: newbie++ > > 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)