Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 98978 invoked from network); 22 Jul 2009 11:24:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Jul 2009 11:24:33 -0000 Received: (qmail 50020 invoked by uid 500); 22 Jul 2009 11:25:38 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 49995 invoked by uid 500); 22 Jul 2009 11:25:38 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 49985 invoked by uid 99); 22 Jul 2009 11:25:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jul 2009 11:25:38 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jul 2009 11:25:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D6C7F234C044 for ; Wed, 22 Jul 2009 04:25:14 -0700 (PDT) Message-ID: <1308804598.1248261914878.JavaMail.jira@brutus> Date: Wed, 22 Jul 2009 04:25:14 -0700 (PDT) From: "Tom White (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Created: (HADOOP-6165) Add metadata to Serializations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Add metadata to Serializations ------------------------------ Key: HADOOP-6165 URL: https://issues.apache.org/jira/browse/HADOOP-6165 Project: Hadoop Common Issue Type: New Feature Components: contrib/serialization Reporter: Tom White Priority: Blocker Fix For: 0.21.0 The Serialization framework only allows a class to be passed as metadata. This assumes there is a one-to-one mapping between types and Serializations, which is overly restrictive. By permitting applications to pass arbitrary metadata to Serializations, they can get more control over which Serialization is used, and would also allow, for example, one to pass an Avro schema to an Avro Serialization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.