cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2710) Get multiple column ranges
Date Thu, 16 Aug 2012 20:03:38 GMT


Vijay commented on CASSANDRA-2710:

>>> multiget-within-a-single-row still has all the problems of multiget-across-rows,
with the added problem that it doesn't parallelize across machines.
Well multiget-within-a-single-row is suppose to be one sequential IO (hence more throughput
at-least for the best case), and the co-ordinator doesn't need to wait for the slowest responding
node (more transient memory in the co-ordinator) etc.
> Get multiple column ranges
> --------------------------
>                 Key: CASSANDRA-2710
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API, Core
>            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:!default.jspa
For more information on JIRA, see:


View raw message