Details
-
Sub-task
-
Status: Resolved
-
Normal
-
Resolution: Won't Fix
-
None
Description
I have replaced all my super column families with regular column families using composite columns. I have easily been able to support all previous functionality (I don't need range delete) except for one thing: getting multiple super columns with a single access. For this, I would need to get multiple ranges. (I can get multiple columns, or a single range, but not multiple ranges.)
For example, I used to have
[<superColumnName1>,<subColumnName1..N>],[<superColumnName2>,<subColumnName1..N>]
and I could get superColumnName1, superColumnName2
Now I have
[<len><superColumnName1>0<len><subColumnName1>..<len><superColumnName1>0<len><subColumnNameN>],[<len><superColumnName2>0<len><subColumnName1>..<len><superColumnName2>0<len><subColumnNameN>]
and I need to get superColumnName1..superColumnName1+, superColumnName2..superColumnName2+
to get the same functionality
I would like the clients to support this functionality, e.g. Hector to have .setRages parallel to .setColumnNames
and for CQL to support a syntax like
SELECT [FIRST N] [REVERSED] name1..nameN1, name2..nameN2... FROM ...