[
https://issues.apache.org/jira/browse/CRUNCH-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451711#comment-13451711
]
Vinod Kumar Vavilapalli commented on CRUNCH-59:
-----------------------------------------------
Oh, yes, I missed the documentation. And one of the code paths too.
bq. configure() is called during the job construction process on the client
side, and provides a mechanism for a DoFn to alter the configuration of an MR
job before it is submitted.
Understand what the documentation refers to now. But shouldn't users instead
set up the configuration via {{Pipeline.setConfiguration()}}. Any use-case that
explicitly needs to overwrite what the rest of crunch-client side does?
> DoFn doesnt' need both configure and initialize methods
> -------------------------------------------------------
>
> Key: CRUNCH-59
> URL: https://issues.apache.org/jira/browse/CRUNCH-59
> Project: Crunch
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
>
> DoFN doesn't seem to need both {{public void configure(Configuration conf)}}
> and {{public void initialize()}}. We can do with a single API like
> {{initialize(Configuration)}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
