Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <11889170.162261272036299545.JavaMail.jira@thor>
Date: Fri, 23 Apr 2010 11:24:59 -0400 (EDT)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6659) Switch RPC to use Avro
In-Reply-To: <387448273.476441269469290584.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860274#action_12860274 ] 

Arun C Murthy commented on HADOOP-6659:
---------------------------------------

Doug, the concern I have is that doing an incremental approach i.e. protocol-by-protocol, exposes us to the risk that a late-breaking bug will leave the projects (HDFS/Map-Reduce) in a state where we can't move forward or back since we have too many changes. I'm sure you see this.

Having said that I do understand it's harder to this in a branch. However, you will find a lot of support to ease the pain - I would be willing to volunteer to help on the Map-Reduce IDL work in the branch, I'm sure we will find others willing to pitch in for HDFS etc. That way we could get the system working end-to-end with Avro, test at scale and merge switch swiftly. Does that sounds reasonable?

> Switch RPC to use Avro
> ----------------------
>
>                 Key: HADOOP-6659
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6659
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Doug Cutting
>
> This is an umbrella issue for moving HDFS and MapReduce RPC to use Avro.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.