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 Mon, 16 Aug 2010 20:20:22 GMT


Jonathan Ellis commented on CASSANDRA-1315:

bq. 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.

This has never been a sure thing, and we're way behind schedule on what we had planned.

Offering both Thrift and Avro here would be fine, that's similar to what our migration path
to Avro was planned to be like anyway.  But even if we were going to switch 100% to Avro we're
several releases away from where that should be the only interface.

> 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