Jimmy,
The secondary index is getting scanned since you put the column in your
query. The behavior you are looking for is a coming feature called Global
Indexes slated for 3.0. https://issues.apache.org/jira/browse/CASSANDRA-6477
In the meantime, you could build your own lookup table even with
Thanks for the suggestion DuyHai. I assume you mean CL=QUORUM (as in
consistency level, not replication factor). As expected, setting the
consistency level to quorum or all yields equally inconsistent results for
the select count and select distinct queries.
Which is good in a way, because if
heh on the midst of upgrading , Rob ;-)
Jason
On Tue, Mar 10, 2015 at 2:04 AM, Robert Coli rc...@eventbrite.com wrote:
On Sat, Mar 7, 2015 at 1:44 AM, Jason Wee peich...@gmail.com wrote:
hey Ali, 1.0.8
On Sat, Mar 7, 2015 at 5:20 PM, Ali Akhtar ali.rac...@gmail.com wrote:
What version are
I am planning to use the Update...USING TIMESTAMP... statement to make sure
that I do not overwrite fresh data with stale data while having to avoid
doing at least LOCAL_QUORUM writes.
Here is my table structure.
Table=DocumentStore
DocumentID (primaryKey, bigint)
Document(text)
Version(int)
If
Or just manually delete the files. The directories are broken down by
keyspace and table.
Patrick
On Mon, Mar 9, 2015 at 7:50 PM, 曹志富 cao.zh...@gmail.com wrote:
nodetool clearsnapshot
--
Ranger Tsao
2015-03-10 10:47 GMT+08:00 鄢来琼 laiqiong@gtafe.com:
