[
https://issues.apache.org/jira/browse/CASSANDRA-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898444#action_12898444
]
Stu Hood commented on CASSANDRA-1315:
-------------------------------------
> other than the codegen step?
Just the codegen step. If you don't have root access to your cluster for
instance, you would need to JAR the Thrift generated code and then use a
relative import to pull it in.
If the real question we're debating is whether we are still considering
switching Cassandra 100% to Avro before 1.0, then we should probably discuss
that elsewhere. When I began this ticket, I was under the impression that that
was a sure thing.
> ColumnFamilyOutputFormat should use client API objects
> ------------------------------------------------------
>
> Key: CASSANDRA-1315
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1315
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Reporter: Stu Hood
> Assignee: Stu Hood
> Fix For: 0.7 beta 2
>
> Attachments: 0001-Use-Avro-objects-as-input-to-CFOutputFormat.patch,
> 0002-Allow-multiple-mutations-per-key-to-arrive-during-in.patch
>
>
> ColumnFamilyOutputFormat currently takes IColumns as its input, meaning that
> users need to understand Cassandra's internals reasonably well in order to
> use it, and need to hardcode things like the comparator type and clock type
> into their MapReduce jobs.
> Instead, CFOutputFormat should take either Thrift or Avro objects, which are
> familiar interfaces for users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
