Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 2918 invoked from network); 20 Jul 2009 19:37:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jul 2009 19:37:32 -0000 Received: (qmail 32996 invoked by uid 500); 20 Jul 2009 19:38:37 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 32948 invoked by uid 500); 20 Jul 2009 19:38:37 -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 32938 invoked by uid 99); 20 Jul 2009 19:38:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jul 2009 19:38:37 +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; Mon, 20 Jul 2009 19:38:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 01C0A234C1E6 for ; Mon, 20 Jul 2009 12:38:15 -0700 (PDT) Message-ID: <1169680547.1248118695006.JavaMail.jira@brutus> Date: Mon, 20 Jul 2009 12:38:15 -0700 (PDT) From: "Doug Cutting (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Commented: (HADOOP-6120) Add support for Avro types in hadoop 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 [ https://issues.apache.org/jira/browse/HADOOP-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733331#action_12733331 ] Doug Cutting commented on HADOOP-6120: -------------------------------------- If, e.g., a class both implements Writable and also either implements AvroReflectSerializeable or whose package is listed in the config, then which serialization is used is determined by the order of the serializers in the config, which could change. Similarly for the Serializeable interface and JavaSerialization. So its not safe to assume that the Class->Serialization map is fixed, and we should really be storing at least the serialization's name in container metadata, and probably also a version (e.g. serialVersionUID for JavaSerialization). And once we have a mechanism to support that, we can also store other metadata, like the schema, so that we can read older versions and generic data. +1 for removing JavaSerialization from the defaults. +1 for a separate Jira on serialization metadata. But it would be best to have such metadata by the 0.21 freeze, in two weeks. > Add support for Avro types in hadoop > ------------------------------------ > > Key: HADOOP-6120 > URL: https://issues.apache.org/jira/browse/HADOOP-6120 > Project: Hadoop Common > Issue Type: New Feature > Reporter: Sharad Agarwal > Assignee: Sharad Agarwal > Attachments: 6120_v1.patch, 6120_v2.patch, 6120_v3.patch, 6120_v4.patch, 6120_v5.patch, HADOOP-6120.patch > > > Support to serialize and deserialize Avro types in Hadoop. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.