[ https://issues.apache.org/jira/browse/FLINK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681584#comment-14681584 ]
ASF GitHub Bot commented on FLINK-1819: --------------------------------------- Github user mxm commented on the pull request: https://github.com/apache/flink/pull/966#issuecomment-129826022 @StephanEwen @fhueske The `Rich` prefix might seem a bit odd but it is a naming convention that is consistent with the user-defined functions which have the RuntimeContext available. As for `abstract classes vs interface` I agree with @sachingoel0101 that it makes sense to implement access to the RuntimeContext once for the user. We may also add other "rich" functions; if we implemented that using an interface we would have to change it later on or add another interface. I think Input/Ouput formats should be "rich" by default. However, we might not want to break the API for existing external implementations. > 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)