[jira] [Commented] (CASSANDRA-11045) Legacy SSTables for KEYS indexes can't be read in 3.0+

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

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

Sam Tunnicliffe commented on CASSANDRA-11045:
---------------------------------------------

||branch||testall||dtest||
|[11045-3.0|https://github.com/beobal/cassandra/tree/11046-5.0]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-11045-3.0-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-11045-3.0-dtest]|

(dtests currently running)

> Legacy SSTables for KEYS indexes can't be read in 3.0+
> ------------------------------------------------------
>
>                 Key: CASSANDRA-11045
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11045
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata, Local Write-Read Paths
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Critical
>             Fix For: 3.0.x, 3.x
>
>
> Trying to read an SSTable for a KEYS index created in 2.1 throws a deserialization error when being read following an upgrade to 3.0. This occurs whether the read comes via the query path or by running {{nodetool upgradesstables}}.



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