cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2710) Get multiple column ranges
Date Sun, 12 Aug 2012 22:34:38 GMT

     [ 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-thrift.patch
    
> 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-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

        

Mime
View raw message