Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Mon, 9 Jun 2014 20:07:02 +0000 (UTC)
From: "Gabriel Reid (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12719087.1402258746403.96924.1402344422981@arcas>
In-Reply-To: <JIRA.12719087.1402258746403@arcas>
References: <JIRA.12719087.1402258746403@arcas>
Subject: [jira] [Updated] (CRUNCH-416) Use Avro built-in deep copying where
 possible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CRUNCH-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid updated CRUNCH-416:
--------------------------------

    Attachment: CRUNCH-416_2.patch

Updated patch with improved testing for null values. This is the one I'll be committing in a few moments.

> Use Avro built-in deep copying where possible
> ---------------------------------------------
>
>                 Key: CRUNCH-416
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-416
>             Project: Crunch
>          Issue Type: Improvement
>            Reporter: Gabriel Reid
>         Attachments: CRUNCH-416.patch, CRUNCH-416_2.patch
>
>
> Avro includes built-in deep-copying for specific and generic records, and this deep-copying isn't based on serialization, which provides quite a bit improvement in performance in some cases.
> We should make use of the built-in deep copying functionality from avro instead of the custom serialization-based code that is currently in place.


--
This message was sent by Atlassian JIRA
(v6.2#6252)