Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <452374798.1260823214813.JavaMail.jira@brutus>
Date: Mon, 14 Dec 2009 20:40:14 +0000 (UTC)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6438) Add configuration getters/setters
 to serialization classes
In-Reply-To: <1372993065.1260584298202.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Doug Cutting commented on HADOOP-6438:
--------------------------------------

> In MAPREDUCE-1126 you suggested that we add these methods directly to WritableSerialization and AvroSerialization.

Sorry, I must have forgotten to put on my project-split goggles!  If they're mapreduce-speciific, then they really belong in that project, I think.

> Should we add a new package that contains a configuration API around serializers?

A package feels like overkill to me.  Do we expect more than a single class?


> Add configuration getters/setters to serialization classes
> ----------------------------------------------------------
>
>                 Key: HADOOP-6438
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6438
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>         Attachments: HADOOP-6438.patch
>
>
> Needed for MAPREDUCE-1126, getter and setter methods to inject specific metadata into configurations to (de)serialize various data types.

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