cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-1315) ColumnFamilyOutputFormat should use client API objects
Date Wed, 25 Aug 2010 20:54:19 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-1315.
---------------------------------------

      Reviewer: jbellis
    Resolution: Fixed

Stu convinced me that due to the direction the Hadoop project is moving, demand for a Thrift
api is likely to be low.  Committed.

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


Mime
View raw message