On Fri, Sep 24, 2010 at 9:15 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > Can you start with the problem you are trying to solve, before we > decide if composite indexes is the right solution? :)
In this case we have a large number of transactions, each with a date, type, detail etc. We are mostly looking for transactions between certain dates that have a certain value in one of the other fields. By maintaining a separate ColumnFamily (index) with a row key of the date + type we can easily find the transactions of a specific type on a certain day. All you need to do is concatenate the date and type, and look up the index. Currently we are maintaining the indexes ourselves. The new server side indexing function looks interesting, but only seems to permit one column. Allowing the index key to be multiple columns concatenated would permit a search based on multiple column values.
