[
https://issues.apache.org/jira/browse/FLINK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653237#comment-14653237
]
ASF GitHub Bot commented on FLINK-1819:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/966#issuecomment-127512155
I am pretty much against `postConfigure()`. There are so many life cycle
methods already, we should really not make it more complicated (I think even
`configure()` is a problem, but that's an artifact).
It is not so hard to make it right in the `open()` method, and there are
methods that getOrCreate accumulators, afaik.
> Allow access to RuntimeContext from Input and OutputFormats
> -----------------------------------------------------------
>
> Key: FLINK-1819
> URL: https://issues.apache.org/jira/browse/FLINK-1819
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime
> Affects Versions: 0.9, 0.8.1
> Reporter: Fabian Hueske
> Priority: Minor
> Fix For: 0.9
>
>
> User function that extend a RichFunction can access a {{RuntimeContext}}
> which gives the parallel id of the task and access to Accumulators and
> BroadcastVariables.
> Right now, Input and OutputFormats cannot access their {{RuntimeContext}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
