Subject: Re: Node selection when both partition key and secondary index
field constrained?
Any query is going to fail quorum + rf3 + 2 nodes down.
One thing about 2x indexes (both user defined and built in) is that
finding an answer using them requires more nodes to be up then just a single
Any query is going to fail quorum + rf3 + 2 nodes down.
One thing about 2x indexes (both user defined and built in) is that finding
an answer using them requires more nodes to be up then just a single get or
slice.
On Monday, January 28, 2013, Mike Sample mike.sam...@gmail.com wrote:
Thanks
@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: Node selection when both partition key and secondary index field
constrained?
Any query is going to fail quorum + rf3 + 2 nodes down.
One thing about 2x indexes (both user defined and built in) is that finding
To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: Node selection when both partition key and secondary index
field constrained?
Any query is going to fail quorum + rf3 + 2 nodes down.
One thing about 2x indexes
@cassandra.apache.org
Date: Wednesday, January 30, 2013 7:31 AM
To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: Node selection when both partition key and secondary index
field constrained?
Any query is going
It uses the index...
cqlsh:dev tracing on;
Now tracing requests.
cqlsh:dev
cqlsh:dev
cqlsh:dev SELECT id, flag from foo WHERE TOKEN(id) '-9939393' AND TOKEN(id)
= '0' AND flag=true;
Tracing session: 128cab90-6982-11e2-8cd1-51eaa232562e
activity |
Thanks Aaron. So basically it's merging the results 2 separate queries:
Indexed scan (token-range) intersect foo.flag_index=true where the
latter query hits the entire cluster as per the secondary index FAQ
entry. Thus the overall query would fail if LOCAL_QUORUM was requested,
RF=3 and 2
