[
https://issues.apache.org/jira/browse/CASSANDRA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902232#action_12902232
]
Stu Hood commented on CASSANDRA-1368:
-------------------------------------
> wouldn't json be an even better fit than thrift or avro?
Thrift and Avro serialization exist because JSON is not a nice way to deal with
tons of data (especially binary data).
> or even simpler: allow specifying separator characters for rows and columns
> (iianm this is what regular hadoop streaming does)
I think you are _seriously_ underestimating the can of worms this would be, and
it wouldn't even get you timestamp support.
> Add output support for Hadoop Streaming
> ---------------------------------------
>
> Key: CASSANDRA-1368
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1368
> Project: Cassandra
> Issue Type: New Feature
> Components: Hadoop
> Reporter: Stu Hood
> Fix For: 0.7 beta 2
>
> Attachments: 0001-Switch-to-Cloudera-s-Distribution-of-Hadoop.patch,
> 0002-Add-an-Avro-OutputReader-and-Resolver-for-Hadoop-Str.patch,
> 0003-Apply-the-deprecated-OutputFormat-interface-to-allow.patch,
> 0004-Add-Streaming-example-shell-scripts.patch
>
>
> Hadoop Streaming is a framework that allows mapreduce jobs to be written in
> languages other than Java, by performing simple IPC on stdin/stdout.
> Adding output support for Hadoop Streaming to Cassandra would mean that users
> could write very simple scripts in dynamic languages to load data into
> Cassandra. Once our Hadoop OutputFormat has stabilized a bit, we might also
> be able to this code to provide scalable bulk loading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
