Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Wed, 22 Jan 2014 02:38:19 +0000 (UTC)
From: "Josh Wills (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12690172.1390358115214.43895.1390358299291@arcas>
In-Reply-To: <JIRA.12690172.1390358115214@arcas>
References: <JIRA.12690172.1390358115214@arcas>
Subject: [jira] [Updated] (CRUNCH-328) Add support for ExtensionRegistry
 with PTypes.protos
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Wills updated CRUNCH-328:
------------------------------

    Attachment: CRUNCH-328.patch

Here's my cut at this.

> Add support for ExtensionRegistry with PTypes.protos
> ----------------------------------------------------
>
>                 Key: CRUNCH-328
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-328
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>            Reporter: Josh Wills
>            Assignee: Josh Wills
>         Attachments: CRUNCH-328.patch
>
>
> Came across a use case where it would be great to be able to have support for deserializing protobufs using an ExtensionRegistry for some custom message extensions. ExtensionRegistry isn't serializable and there isn't a good way to serialize it using the current protobuf libraries, so I also created a Serializable extension of Guava's Supplier interface to handle cases where we need to specify how to construct an object for use in a DoFn as an external argument, which seemed fairly useful.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)