[
https://issues.apache.org/jira/browse/CASSANDRA-13119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ariel Weisberg updated CASSANDRA-13119:
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.11.x)
(was: 4.x)
(was: 3.0.x)
(was: 2.2.x)
2.2.10
Status: Resolved (was: Ready to Commit)
Committed as
[6c5ea192c75072ba3f7369dfc23592d6ed0c319f|https://github.com/apache/cassandra/commit/6c5ea192c75072ba3f7369dfc23592d6ed0c319f]
> dtest failure
> upgrade_tests.upgrade_supercolumns_test.TestSCUpgrade.upgrade_super_columns_through_all_versions_test
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13119
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13119
> Project: Cassandra
> Issue Type: Bug
> Components: Core, Testing
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Priority: Critical
> Fix For: 2.2.10
>
>
> The test complains about unreadable sstables version ka and lb during upgrade
> which is 2.1 and 2.2. These tables look like system tables not user tables.
> I looked and I can't find any place where system tables are upgraded on
> upgrade. You can specify them explicitly by name with nodetool, but nodetool
> defaults to only upgrading user tables and doesn't have a flag to upgrade all
> tables.
> These tables probably need to be removed if unused or upgraded if in use.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
