You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/04/20 09:45:25 UTC
[jira] [Commented] (FLINK-3789) Overload methods which trigger
program execution to allow naming job
[ https://issues.apache.org/jira/browse/FLINK-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249436#comment-15249436 ]
Robert Metzger commented on FLINK-3789:
---------------------------------------
In general, I think we need to provide an API for passing a job name with these methods as well.
However, I'm wondering if its a good idea to have too many overloaded methods on the DataSet classes. Maybe adding a ExecutionEnvironment.setDefaultJobname(String) would do the job as well?
> Overload methods which trigger program execution to allow naming job
> --------------------------------------------------------------------
>
> Key: FLINK-3789
> URL: https://issues.apache.org/jira/browse/FLINK-3789
> Project: Flink
> Issue Type: Improvement
> Components: Java API
> Affects Versions: 1.1.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Priority: Minor
>
> Overload the following functions to additionally accept a job name to pass to {{ExecutionEnvironment.execute(String)}}.
> * {{DataSet.collect()}}
> * {{DataSet.count()}}
> * {{DataSetUtils.checksumHashCode(DataSet)}}
> * {{GraphUtils.checksumHashCode(Graph)}}
> Once the deprecated {{DataSet.print(String)}} and {{DataSet.printToErr(String)}} are removed we can overload {{DataSet.print()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)