[
https://issues.apache.org/jira/browse/CASSANDRA-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay updated CASSANDRA-2710:
-----------------------------
Attachment: 0001-2710-multiple-column-ranges-cql.patch
CQL part.
cqlsh:Keyspace1> select 0 .. 2,3 from Standard1 where key = 100;
Bad Request: line 1:16 mismatched input 'from' expecting RANGEOP
cqlsh:Keyspace1> select 0 .. 2,3 .. 0 from Standard1 where key = 100;
Bad Request: Slice finish must come after start in traversal order
cqlsh:Keyspace1> select 0 .. 2,3 .. '' from Standard1 where key = 100;
0 | 1 | 10 | 11 | 12 | 13 | 14 | 15 | 16
| 17 | 18 | 19 | 2 | 3 | 30 | 31 | 32 | 33
| 34 | 35 | 36 | 37 | 38 | 39 | 4 | 40 | 41
| 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 5
| 50 ...
> Get multiple column ranges
> --------------------------
>
> Key: CASSANDRA-2710
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2710
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: David Boxenhorn
> Assignee: Vijay
> Labels: compositeColumns, cql
> Attachments: 0001-2710-multiple-column-ranges-cql.patch,
> 0001-2710-multiple-column-ranges-thrift.patch
>
>
> 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 ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
