You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2015/04/08 14:11:12 UTC
[jira] [Commented] (FLINK-1819) Allow access to RuntimeContext from
Input and OutputFormats
[ https://issues.apache.org/jira/browse/FLINK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485163#comment-14485163 ]
Stephan Ewen commented on FLINK-1819:
-------------------------------------
I agree, that would be a very good addition.
Since Input/Output formats are interfaces, what is the best place to hand over the runtime context?
Ideas:
- Pass it to the {{open()}} method as an additional argument (API breaking)
- make formats implement a special interface {{ContextAware}} that defines a {{setRuntimeContext()}} method.
> 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)