You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/10/03 15:51:00 UTC

[jira] [Updated] (CASSANDRA-17944) Extend testing for test_sstableupgrade

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

Ekaterina Dimitrova updated CASSANDRA-17944:
--------------------------------------------
    Change Category: Quality Assurance
         Complexity: Normal
        Component/s: CI
             Status: Open  (was: Triage Needed)

> Extend testing for test_sstableupgrade
> --------------------------------------
>
>                 Key: CASSANDRA-17944
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17944
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Ekaterina Dimitrova
>            Priority: Normal
>
> While looking into another problem I noticed the below comment and I did not find expansion of this coverage, the particular test still ends in 3.X. Maybe we test in the in-jvm? To be checked. 
> {code:java}
> # 4.0 removes back compatibility with pre-3.0 versions, so testing upgradesstables for
> # paths from those versions to 4.0 is invalid (and can only fail). There isn't currently
> # any difference between the 3.0 and 4.0 sstable format though, but when the version is
> # bumped for 4.0, remove the max_version & add a case for testing a 3.0 -> 4.0 upgrade
> @since('2.2', max_version='3.X')
> def test_sstableupgrade(self):{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org