Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 25 Jan 2016 14:56:39 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12932696.1453294396000.200828.1453733799906@Atlassian.JIRA>
In-Reply-To: <JIRA.12932696.1453294396000@Atlassian.JIRA>
References: <JIRA.12932696.1453294396000@Atlassian.JIRA>
 <JIRA.12932696.1453294396367@arcas>
Subject: [jira] [Updated] (CASSANDRA-11045) Legacy SSTables for KEYS indexes
 can't be read in 3.0+
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sylvain Lebresne updated CASSANDRA-11045:
-----------------------------------------
    Reviewer: Sylvain Lebresne

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