[
https://issues.apache.org/jira/browse/FLINK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694974#comment-14694974
]
ASF GitHub Bot commented on FLINK-1819:
---------------------------------------
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/966#issuecomment-130595336
Thank you for your remarks @StephanEwen.
>I think you should go ahead and just call them "Rich". It is just a name,
and what matters is that the JavaDocs describe what it actually means...
The JavaDocs in this pull request properly describe what a
"RichInputFormat" is. So we are good to go. Let's stick with "Rich" although I
understand your concerns.
I'll merge this later if nobody objects in the meantime :)
> 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
> Assignee: Sachin Goel
> 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)
