Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Not A Problem
-
None
Description
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.