[
https://issues.apache.org/jira/browse/FLINK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651031#comment-14651031
]
ASF GitHub Bot commented on FLINK-1819:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/966#issuecomment-127032323
Would not not be much simpler to add an interface `RuntimeContextFormat`
with a method (`setRuntimeContext()`) and call this method on the formats that
implement this interface? That would be three changed classes, done.
I am also a bit sceptical about the difference between input format and
rich input format. For transformation functions the difference between Function
(a lambda) and RichFunction (many mode methods) makes sense. Input formats are
per-se pretty rich...
> 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)
