You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/07 12:41:21 UTC
[jira] [Commented] (FLINK-3978) Add hasBroadcastVariable method to
RuntimeContext
[ https://issues.apache.org/jira/browse/FLINK-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318399#comment-15318399 ]
ASF GitHub Bot commented on FLINK-3978:
---------------------------------------
Github user greghogan closed the pull request at:
https://github.com/apache/flink/pull/2039
> Add hasBroadcastVariable method to RuntimeContext
> -------------------------------------------------
>
> Key: FLINK-3978
> URL: https://issues.apache.org/jira/browse/FLINK-3978
> Project: Flink
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Priority: Minor
> Fix For: 1.1.0
>
>
> The javadocs for {{RuntimeContext}} state that {{getAccumulator}} "throws an exception if the accumulator does not exist or if the accumulator exists, but with different type", although {{AbstractRuntimeUDFContext}} does not throw an exception but will return null.
> The javadocs for {{getBroadcastVariable}} do not mention throwing an exception. Currently the only way to handle a broadcast variable that that may or may not exist is to catch and ignore the exception. Adding a {{containsBroadcastVariable}} method to {{RuntimeContext}} would make this explicit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)