[
https://issues.apache.org/jira/browse/CASSANDRA-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181897#comment-13181897
]
Mck SembWever commented on CASSANDRA-2878:
------------------------------------------
We need the combination of secondary indexes and super columns. My
understanding is implementing any of 1,2,3 won't provide support for super
columns.
So my vote and hopes is on (4). It is simple, and CqlInputFormat can be
written in addition...
This also begs the question: how will supercolumns be handled post-Thrift
(CASSANDRA-2478)?
> 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
