[
https://issues.apache.org/jira/browse/CASSANDRA-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460797#comment-13460797
]
Robbie Strickland commented on CASSANDRA-4208:
----------------------------------------------
[~mkjellman] your usage is correct. What this patch does is actually change
the ConfigHelper so set/getColumnFamily() operates on the
mapreduce.output.basename key that MultipleOutputs (and FileInput/OutputFormat)
uses when it's looking for outputs. This is a bit hacky but unavoidable since
methods to alter this through the Hadoop API are inaccessible. I have a
related ticket on the Hadoop side to change this and make it more generic, but
until then this will have to do.
> ColumnFamilyOutputFormat should support writing to multiple column families
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-4208
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4208
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Affects Versions: 1.1.0
> Reporter: Robbie Strickland
> Attachments: cassandra-1.1-4208.txt, cassandra-1.1-4208-v2.txt,
> cassandra-1.1-4208-v3.txt, cassandra-1.1-4208-v4.txt, trunk-4208.txt,
> trunk-4208-v2.txt
>
>
> It is not currently possible to output records to more than one column family
> in a single reducer. Considering that writing values to Cassandra often
> involves multiple column families (i.e. updating your index when you insert a
> new value), this seems overly restrictive. I am submitting a patch that
> moves the specification of column family from the job configuration to the
> write() call in ColumnFamilyRecordWriter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
