There has to be one equality clause in there, and thats the thing to cassandra uses to select of disk. The others are in memory filters.
So if you have one on the year+month you can have a simple select clause and it limits the amount of data that has to be read. If you have like many 10's to 100's millions of things in the same month you may want to do some performance testing. There can still be times when you want to support common read paths by using custom / hand rolled indexes. Cheers ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 9/01/2013, at 6:05 AM, stephen.m.thomp...@wellsfargo.com wrote: > Hi folks – > > Question about secondary indexes. How are people doing date indexes? I > have a date column in my tables in RDBMS that we use frequently, such as look > at all records recorded in the last month. What is the best practice for > being able to do such a query? It seems like there could be an advantage to > adding a couple of columns like this: > > {timestamp=2013/01/08 12:32:01 -0500} > {month=201301} > {day=08} > > And then I could do secondary index on the month and day columns? Would that > be the best way to do something like this? Is there any accepted “best > practice” on this yet? > > Thanks! > Steve
