Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1800193578.1260826998297.JavaMail.jira@brutus>
Date: Mon, 14 Dec 2009 21:43:18 +0000 (UTC)
From: "Aaron Kimball (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=12790388#action_12790388 ] 

Aaron Kimball commented on HADOOP-6438:
---------------------------------------

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

Depends? There are currently two ways to set the metadata: In most cases, setting the serialized class name is sufficient. (e.g., JavaSerialization, WritableSerialization, AvroSpecificSerialization). In the AvroGenericSerialization case, though, we set the schema to serialize, using an analogous but distinct API. We could maybe add a single class that contains methods like {{setMapOutputKeyClass()}} and {{setMapOutputKeySchema()}}; the current implementation breaks these apart, making the serialization system being used more explicit in the class name to which the configuration method belongs. I could go either way on this issue.

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