You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Micah Whitacre (JIRA)" <ji...@apache.org> on 2014/03/04 17:54:20 UTC
[jira] [Resolved] (CRUNCH-357) Allow AvroMode overrides to be less
global
[ https://issues.apache.org/jira/browse/CRUNCH-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Micah Whitacre resolved CRUNCH-357.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.8.3
0.10.0
Code changes have been pushed to master and the 0.8 branch.
> Allow AvroMode overrides to be less global
> ------------------------------------------
>
> Key: CRUNCH-357
> URL: https://issues.apache.org/jira/browse/CRUNCH-357
> Project: Crunch
> Issue Type: Improvement
> Components: Core, IO
> Reporter: Micah Whitacre
> Assignee: Micah Whitacre
> Fix For: 0.10.0, 0.8.3
>
> Attachments: CRUNCH-357.patch, CRUNCH-357_immutable.patch, CRUNCH-357_immutable_with_doctests.patch
>
>
> Currently consumers wanting to specify a custom reader must globally override the ReaderFactory for a specific mode. This means that if one AvroFileSource changes the factory it could affect all other sources in the pipeline without anyone knowing it.
> One thought was what if a consumer could get a "local" AvroMode instance, configure it to their needs and then specify that mode to the AvroFileSource to configure that source without changing any global state.
--
This message was sent by Atlassian JIRA
(v6.2#6252)