[
https://issues.apache.org/jira/browse/CASSANDRA-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053467#comment-13053467
]
Mck SembWever edited comment on CASSANDRA-1125 at 6/23/11 8:00 AM:
-------------------------------------------------------------------
For now (without CASSANDRA-1600) I can use a {{KeyRange}} and
{{Range.intersectionWith(..)}} for start/end rowKey limits in CFIF.
To upgrade from KeyRange to IndexClause (once it contains an optional KeyRange
field) can be easily enough done latter by replacing
ConfigHelper.setInputKeyRange(..) to ConfigHelper.setInputIndexClause(..) and
rewriting the code two lines of code in CFRR's RowIterator.maybeInit(..)
was (Author: michaelsembwever):
I can use a {{KeyRange}} and {{Range.intersectionWith(..)}} for start/end
rowKey limits in CFIF.
-And i can use a {{IndexClause}} (which also permits a start_key) and then
{{get_indexed_slices(..)}} in CFRR's {{RowIterator.maybeInit()}} But both
approaches can't be combined. So i guess ConfigHelper could have methods
setInputKeyRange(..) and setInputIndexClause(..) which are mutually exclusive
to call.- Spoke a little early here about using {{get_indexed_slices}}. I can't
see how IndexClause can specify a start/end rowKey - is this possible? (it
needs to to pass through the batch's range)
> Filter out ColumnFamily rows that aren't part of the query
> ----------------------------------------------------------
>
> Key: CASSANDRA-1125
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1125
> Project: Cassandra
> Issue Type: New Feature
> Components: Hadoop
> Reporter: Jeremy Hanna
> Assignee: Mck SembWever
> Priority: Minor
> Fix For: 1.0
>
>
> Currently, when running a MapReduce job against data in a Cassandra data
> store, it reads through all the data for a particular ColumnFamily. This
> could be optimized to only read through those rows that have to do with the
> query.
> It's a small change but wanted to put it in Jira so that it didn't fall
> through the cracks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
