Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <774163554.129011262983075406.JavaMail.jira@brutus.apache.org>
Date: Fri, 8 Jan 2010 20:37:55 +0000 (UTC)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Resolved: (AVRO-278) use array instead of map to implement
 generic records
In-Reply-To: <408398459.1262300789552.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/AVRO-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting resolved AVRO-278.
-------------------------------

      Resolution: Fixed
    Release Note: GenericRecord no longer implements Map.
    Hadoop Flags: [Incompatible change, Reviewed]

I just committed this.

> use array instead of map to implement generic records
> -----------------------------------------------------
>
>                 Key: AVRO-278
>                 URL: https://issues.apache.org/jira/browse/AVRO-278
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Doug Cutting
>             Fix For: 1.3.0
>
>         Attachments: AVRO-278.patch, AVRO-278.patch
>
>
> It would be considerably faster to implement GenericData.Record as an array rather than as a HashMap.  We expect generic data to be a major incentive to using Avro, and users of Java's generic API should not pay a performance penalty.

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