StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCassandra CQL time range query
text
Body
copied!<p>I have a Cassandra column family where I am storing a large number (hundreds of thousands) of events per month with timestamp (“Ymdhisu”) as the row key. It has multiple columns capturing some data for each event. I tried retrieving events data for a specific time range. For example for the month of Jan, I used the following CQL query:</p> <p>a) Query between range Jan 1- Jan 15, 2013</p> <blockquote> <p>select count(*) from Test where Key > 20130101070100000000 and Key < 20130115070100000000 limit 100000; Bad Request: Start key's md5 sorts after end key's md5. This is not allowed; you probably should not specify end key at all, under RandomPartitioner</p> </blockquote> <p>b) Query between range Jan 1- Jan 10, 2013</p> <blockquote> <p>select count(*) from Test where Key > 20130101070100000000 and Key < 20130110070100000000 limit 100000; count - 73264</p> </blockquote> <p>c) Query between range Jan 1- Jan 2, 2013 </p> <blockquote> <p>select count(*) from Test where Key > 20130101070100000000 and Key < 20130102070100000000 limit 100000; count - 78328</p> </blockquote> <p>It appears as though the range search simply is not working! The schema of my Columnfamily is:</p> <pre><code>Create column family Test with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type AND compression_options={sstable_compression:SnappyCompressor, chunk_length_kb:64}; </code></pre> <p>To extract data, what are the suggestions? Do I need to redefine my schema with key validation class as TimeUUID type? Is there any other way to query efficiently without changing the schema? I am dealing with at least 100-200K rows of data monthly in this column family. If this schema does not work for this purpose, what would be an appropriate Cassandra schema to store and retrieve the kind of data described here?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload