cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3540) Wrong check of partitioner for secondary indexes
Date Thu, 01 Dec 2011 08:27:40 GMT


Yuki Morishita updated CASSANDRA-3540:

    Attachment: cassandra-1.0-3540.txt

This bug is caused by SSTableMetadata providing node's partitioner when reading old version
(prior hc) of sstable.

Attached patch let SSTableMetadata to use empty string("") instead of DatabaseDescriptor.getPartitioner
as default. When older version of sstable is read, SSTableMetadata provides empty string for
partitioner, and check for partitioner is skipped.
> Wrong check of partitioner for secondary indexes
> ------------------------------------------------
>                 Key: CASSANDRA-3540
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.4
>            Reporter: Sylvain Lebresne
>            Assignee: Yuki Morishita
>            Priority: Critical
>             Fix For: 1.0.6
>         Attachments: cassandra-1.0-3540.txt
> CASSANDRA-3407 doesn't handle the fact that secondary indexes have a specific partitioner
(LocalPartitioner). This result in the following error when starting nodes in 1.0.4:
> {noformat}
> java.lang.RuntimeException: Cannot open /var/lib/cassandra/data/Index/AttractionLocationCategoryDateIdx.AttractionLocationCategoryDateIdx_09partition_idx-h-1
because partitioner does not match org.apache.cassandra.dht.LocalPartitioner
> {noformat}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message