[ 
https://issues.apache.org/jira/browse/CASSANDRA-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Ellis updated CASSANDRA-2710:
--------------------------------------

         Reviewer: xedin
      Component/s: Core
                   API
    Fix Version/s: 1.2
    
> Get multiple column ranges
> --------------------------
>
>                 Key: CASSANDRA-2710
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2710
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API, Core
>            Reporter: David Boxenhorn
>            Assignee: Vijay
>              Labels: compositeColumns, cql
>             Fix For: 1.2
>
>         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

        

Reply via email to