[
https://issues.apache.org/jira/browse/CASSANDRA-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2878:
--------------------------------------
Description:
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.
Adding CQL support to m/r will allow using an index more simply than trying to
cram support for more parameters into the job configuration.
was:
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.
Summary: Allow CQL-based map/reduce (was: Filter out ColumnFamily rows
that aren't part of the query (using a IndexClause))
> Allow CQL-based map/reduce
> --------------------------
>
> Key: CASSANDRA-2878
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2878
> Project: Cassandra
> Issue Type: New Feature
> Components: Hadoop
> Reporter: Mck SembWever
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.1
>
>
> 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.
> Adding CQL support to m/r will allow using an index more simply than trying
> to cram support for more parameters into the job configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
