[
https://issues.apache.org/jira/browse/CASSANDRA-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-1125:
--------------------------------------
Attachment: 1125-formatted.txt
Looks good to me for the most part. (Attaching reformatted version.)
One part though I'm not 100% sure about -- we're using KeyRange for
start-exclusive ranges, when the Thrift API always uses it for start-inclusive.
I'd be more comfortable with any of:
- using a Pair<String, String>
- using a new one-off class
- using KeyRange but with tokens (which Thrift also uses for start-exclusive)
- using a Range object directly (also requires tokens)
> 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
>
> Attachments: 1125-formatted.txt, CASSANDRA-1125.patch
>
>
> 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
