Hi guys, I'm in the process of scheduling some time to re-work the query logic in my Hector JPA plugin. A lot of the documentation around CQL on the site seems to indicate that this is the future path of the client interfaces for Cassandra. I have a couple of questions.
1. Will CQL ultimately replace thrift as a client api? 2. If CQL will become the interface, has any thought been given to order by and rownum equivalent functionality in CQL? This seems like a major requirement for most webapps when dealing with secondary indexing and paging. Currently I handle this with dynamic composites, and build a secondary query index with ordering via columns by adding order fields between the indexed fields and the RK in my column. Would something like this be possible directly in Cassandra, or would Lucene style iterators be preferred? Personally, I prefer to take the disk space hit and construct the ordering at the column level. 3. Do you guys feel I should focus efforts on improving the CQL functionality then migrating the JPA plugin to it, or do you feel it is too early to begin using the JDBC CQL drivers for this type of functionality? Thanks guys, Todd
