[
https://issues.apache.org/jira/browse/CASSANDRA-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever reopened CASSANDRA-1125:
--------------------------------------
Something broke here in production once we went out with 0.8.2. It may have
been some poor testing, i'm not entirely sure and a little surprised.
CFIF:135 breaks because inside {{dhtRange.intersects(jobRange)}} there's a call
to {{new Range(token, token)}} which calls {{StorageService.getPartitioner()}}
and StorageService is null as we're not inside the server.
A quick fix (tested) is to change Range:148 from {{new Range(token, token)}} to
{{new Range(token, token, partitioner)}} making the presumption that the
partitioner for the new Range will be the same as this Range.
> Filter out ColumnFamily rows that aren't part of the query (using a KeyRange)
> -----------------------------------------------------------------------------
>
> 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: 0.8.2
>
> Attachments: 1125-formatted.txt, 1125-v3.txt, CASSANDRA-1125.patch,
> 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
