cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Created: (CASSANDRA-1600) Merge get_indexed_slices with get_range_slices
Date Mon, 11 Oct 2010 02:42:10 GMT
Merge get_indexed_slices with get_range_slices
----------------------------------------------

                 Key: CASSANDRA-1600
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1600
             Project: Cassandra
          Issue Type: Improvement
          Components: API
            Reporter: Stu Hood
            Priority: Critical
             Fix For: 0.7.0


>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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message