Thanks for your response, Cyril. Yeah, I realized shortly after asking that
indeed the second term is not being indexed, so it must be doing a table
scan. Indexing for composite columns is in the works (
https://issues.apache.org/jira/browse/CASSANDRA-3680), but not sure how
soon that will be avail
I'm not much advanced in cassandra, but seeing the pycassa doc
http://pycassa.github.com/pycassa/assorted/composite_types.html, for
composites you can't even search for the second term, you need a first
term, the second will filter, you just do range slices on the composite
columns
it's totally di
Suppose I have a table in CQL3 with a 2 part composite, and I do a select
that specifies just the second part of the key (not the partition key),
will this result in a full table scan, or is the second part of the key
indexed?
Example:
cqlsh:"Keyspace1"> CREATE TABLE test_table (part1 text, part2
