[
https://issues.apache.org/jira/browse/CASSANDRA-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901452#action_12901452
]
Stu Hood commented on CASSANDRA-1315:
-------------------------------------
> Offering both Thrift and Avro here would be fine
Hm, I think I could get behind that... aside from proliferation concerns. We'd
be signing up for a ThriftColumnFamilyOutputFormat and an AvroC..F..O..F.., one
of which wrapped the other.
> 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.
