[jira] [Updated] (CASSANDRA-9181) Improve index versus secondary index selection
[ https://issues.apache.org/jira/browse/CASSANDRA-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-9181: - Fix Version/s: (was: 3.x) > Improve index versus secondary index selection > -- > > Key: CASSANDRA-9181 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9181 > Project: Cassandra > Issue Type: Improvement >Reporter: Jeremy Hanna > Labels: 2i > > There is a special case for secondary indexes if you always supply the > partition key. For example, if you have a family with ID "a456" which has 6 > family members and I have a secondary index on first name. Currently, if I > do a query like this "select * from families where id = 'a456' and firstname > = 'alowishus';" you can see from a query trace, that it will first scan the > entire cluster based on the firstname, then look for the key within that. > If it's not terribly invasive, I think this would be a valid use case to > narrow down the results by key first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-9181) Improve index versus secondary index selection
[ https://issues.apache.org/jira/browse/CASSANDRA-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-9181: - Issue Type: Improvement (was: Bug) > Improve index versus secondary index selection > -- > > Key: CASSANDRA-9181 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9181 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Jeremy Hanna > Labels: 2i > Fix For: 3.x > > > There is a special case for secondary indexes if you always supply the > partition key. For example, if you have a family with ID "a456" which has 6 > family members and I have a secondary index on first name. Currently, if I > do a query like this "select * from families where id = 'a456' and firstname > = 'alowishus';" you can see from a query trace, that it will first scan the > entire cluster based on the firstname, then look for the key within that. > If it's not terribly invasive, I think this would be a valid use case to > narrow down the results by key first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9181) Improve index versus secondary index selection
[ https://issues.apache.org/jira/browse/CASSANDRA-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-9181: --- Fix Version/s: 3.0 Labels: 2i (was: ) Improve index versus secondary index selection -- Key: CASSANDRA-9181 URL: https://issues.apache.org/jira/browse/CASSANDRA-9181 Project: Cassandra Issue Type: Bug Components: Core Reporter: Jeremy Hanna Labels: 2i Fix For: 3.0 There is a special case for secondary indexes if you always supply the partition key. For example, if you have a family with ID a456 which has 6 family members and I have a secondary index on first name. Currently, if I do a query like this select * from families where id = 'a456' and firstname = 'alowishus'; you can see from a query trace, that it will first scan the entire cluster based on the firstname, then look for the key within that. If it's not terribly invasive, I think this would be a valid use case to narrow down the results by key first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9181) Improve index versus secondary index selection
[ https://issues.apache.org/jira/browse/CASSANDRA-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-9181: Reproduced In: 2.0.7 Improve index versus secondary index selection -- Key: CASSANDRA-9181 URL: https://issues.apache.org/jira/browse/CASSANDRA-9181 Project: Cassandra Issue Type: Bug Components: Core Reporter: Jeremy Hanna Labels: 2i Fix For: 3.0 There is a special case for secondary indexes if you always supply the partition key. For example, if you have a family with ID a456 which has 6 family members and I have a secondary index on first name. Currently, if I do a query like this select * from families where id = 'a456' and firstname = 'alowishus'; you can see from a query trace, that it will first scan the entire cluster based on the firstname, then look for the key within that. If it's not terribly invasive, I think this would be a valid use case to narrow down the results by key first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
