[jira] [Resolved] (KAFKA-7175) Make version checking logic more flexible in streams_upgrade_test.py

["Matthias J. Sax (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias J. Sax resolved KAFKA-7175.
------------------------------------
      Assignee:     (was: Ray Chiang)
    Resolution: Abandoned

Closing this very old ticket. Seems there test was just find for the last years.

> 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
>            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
(v8.20.10#820010)