cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-1600) Merge get_indexed_slices with get_range_slices
Date Thu, 01 Dec 2011 19:54:40 GMT


Jeremy Hanna commented on CASSANDRA-1600:

Is this going to get done for 1.1 now that CASSANDRA-1034 is committed?
> Merge get_indexed_slices with get_range_slices
> ----------------------------------------------
>                 Key: CASSANDRA-1600
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Stu Hood
>             Fix For: 1.1
>         Attachments: 0001-Add-optional-FilterClause-to-KeyRange-and-support-do-v2.patch,
0001-Add-optional-FilterClause-to-KeyRange-and-support-doin.txt, 0002-allow-get_range_slices-to-apply-filter-to-a-sequenti-v2.patch,
> From a comment on 1157:
> {quote}
> IndexClause only has a start key for get_indexed_slices, but it would seem that the reasoning
behind using 'KeyRange' for get_range_slices applies there as well, since if you know the
range you care about in the primary index, you don't want to continue scanning until you exhaust
'count' (or the cluster).
> Since it would appear that get_indexed_slices would benefit from a KeyRange, why not
smash get_(range|indexed)_slices together, and make IndexClause an optional field on KeyRange?
> {quote}

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