[
https://issues.apache.org/jira/browse/FLINK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659005#comment-14659005
]
ASF GitHub Bot commented on FLINK-1819:
---------------------------------------
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/966#issuecomment-128157289
Hi @sachingoel0101,
Thanks for the update! The PR looks good in general.
Regarding the interface vs. abstract class issue, I am a bit undecided with
a slight preference towards the abstract class. However, I agree with
@StephanEwen that `RichInputFormat` and `RichOutputFormat` are not good names.
How about `ContextInputFormat` and `ContextOutputFormat`?
Any other opinions on that matter?
> 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)
