[ https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510754#comment-14510754 ]
ASF GitHub Bot commented on FLINK-1486: --------------------------------------- Github user mxm commented on the pull request: https://github.com/apache/flink/pull/372#issuecomment-95880258 Yes, it should be simple for the user. It makes sense to have one print method which just prints the output on the client. In addition, we could have another *advanced* print method which prints a prefix and optionally the task id. - `print()` - `print(String prefix, boolean includeParallelID)` > Add a string to the print method to identify output > --------------------------------------------------- > > Key: FLINK-1486 > URL: https://issues.apache.org/jira/browse/FLINK-1486 > Project: Flink > Issue Type: Improvement > Components: Local Runtime > Reporter: Maximilian Michels > Assignee: Maximilian Michels > Priority: Minor > Labels: usability > Fix For: 0.9 > > > The output of the {{print}} method of {[DataSet}} is mainly used for debug > purposes. Currently, it is difficult to identify the output. > I would suggest to add another {{print(String str)}} method which allows the > user to supply a String to identify the output. This could be a prefix before > the actual output or a format string (which might be an overkill). > {code} > DataSet data = env.fromElements(1,2,3,4,5); > {code} > For example, {{data.print("MyDataSet: ")}} would output print > {noformat} > MyDataSet: 1 > MyDataSet: 2 > ... > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)