cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11045) Legacy SSTables for KEYS indexes can't be read in 3.0+
Date Mon, 25 Jan 2016 15:32:39 GMT

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

Sylvain Lebresne commented on CASSANDRA-11045:
----------------------------------------------

+1 (pending test results of course)

> 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)

Mime
View raw message