[ https://issues.apache.org/jira/browse/CASSANDRA-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160787#comment-13160787 ]
Sylvain Lebresne commented on CASSANDRA-3540: --------------------------------------------- Some nits: * We can give then partitioner as an argument to Collector.finalizeMetadata() instead of adding a new field. * I think I slightly prefer using null when there is no partitioner available. I understand that "" make SSTableMetadata slightly simpler but in fact we shouldn't ever write a SSTableMetadata with no partitioner (we can only read one). So we could simply assert that partitioner != null in the serialize method. > Wrong check of partitioner for secondary indexes > ------------------------------------------------ > > Key: CASSANDRA-3540 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3540 > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira