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/02/26 04:38:20 UTC

[jira] [Updated] (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 updated CRUNCH-357:
----------------------------------

    Summary: Allow AvroMode overrides to be less global  (was: Allows AvroMode overrides to be less global)

> 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: Josh Wills
>
> 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.1.5#6160)