[jira] [Updated] (CASSANDRA-3123) Don't try to build secondary indexes when there is none
[ https://issues.apache.org/jira/browse/CASSANDRA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-3123: Attachment: 3123.patch Attaching patch against 0.8. It makes buildSecondaryIndexes just return if there is no indexed columns. Don't try to build secondary indexes when there is none --- Key: CASSANDRA-3123 URL: https://issues.apache.org/jira/browse/CASSANDRA-3123 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.8.0 Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Trivial Fix For: 0.8.5 Attachments: 3123.patch buildSecondaryIndexes() is sometimes called without checking the cfs has secondary indexes. Has a result, it prints a useless message and will trigger a bunch of useless action (among which, a full scan of the indexed column family). This is not a huge problem in 0.8 because only the fairly new loadNewSSTables() call does this (which doesn't mean we should fix it). But in trunk, it does this after every streamIn session. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3123) Don't try to build secondary indexes when there is none
[ https://issues.apache.org/jira/browse/CASSANDRA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-3123: Attachment: 3123-v2.patch Updated patch with proposed changes Don't try to build secondary indexes when there is none --- Key: CASSANDRA-3123 URL: https://issues.apache.org/jira/browse/CASSANDRA-3123 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.8.0 Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Trivial Fix For: 0.8.5 Attachments: 3123-v2.patch, 3123.patch buildSecondaryIndexes() is sometimes called without checking the cfs has secondary indexes. Has a result, it prints a useless message and will trigger a bunch of useless action (among which, a full scan of the indexed column family). This is not a huge problem in 0.8 because only the fairly new loadNewSSTables() call does this (which doesn't mean we should fix it). But in trunk, it does this after every streamIn session. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
