cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1315) ColumnFamilyOutputFormat should use client API objects
Date Thu, 12 Aug 2010 19:24:19 GMT


Jonathan Ellis commented on CASSANDRA-1315:

reverted commit of 0001 after looking at CASSANDRA-1368 more.

I'm less and less convinced that we're going to move go Avro as our "main" interface, and
unless we are, we shouldn't be adding public dependencies on it.

I don't buy the argument that "Hadoop people already know Avro" because there's basically
nothing here that's a standard Hadoop Avro class, and using a Thrift StreamingMutation class
would be much the same as an Avro one.

> ColumnFamilyOutputFormat should use client API objects
> ------------------------------------------------------
>                 Key: CASSANDRA-1315
>                 URL:
>             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.

View raw message