kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks
Date Tue, 29 Nov 2016 09:57:58 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704851#comment-15704851
] 

Ismael Juma commented on KAFKA-4450:
------------------------------------

It would be good to understand what [~ewencp] meant as I may be missing something.

My understanding is that we currently test upgrades between major and minor versions (e.g.
0.9.0.2 to 0.10.0.0,  0.10.0.1 to 0.10.1.x, etc.). If we are happy with that, then I think
there is nothing to be done for 0.10.1.1 (just trunk). If we want to test upgrades between
patch versions, then we need to add 0.10.1.0 as a source in the 0.10.1 branch so that we test
0.10.1.0 to 0.10.1.1 (for example).

> Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-4450
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4450
>             Project: Kafka
>          Issue Type: Bug
>          Components: system tests
>    Affects Versions: 0.10.1.0
>            Reporter: Ewen Cheslack-Postava
>            Priority: Critical
>             Fix For: 0.10.1.1, 0.10.2.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> We have upgrade system tests, but we neglected to update them for the most recent released
versions (we only have LATEST_0_10_0 but not something from 0_10_1).
> We should probably not only add these versions, but also a) make sure some TRUNK version
is always included since upgrade to trunk would always be possible to avoid issues for anyone
deploying off trunk (we want every commit to trunk to be solid & compatible) and b) make
sure there aren't gaps between versions annotated on the test vs versions that are officially
released (which may not be easy statically with the decorators, but might be possible by checking
the kafkatest version against previous versions and checking for gaps?).
> Perhaps we need to be able to get the most recent release/snapshot version from the python
code so we can always validate previous versions? Even if that's possible, is there going
to be a reliable way to get all the previous released versions so we can make sure we have
all upgrade tests in place?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message