[ 
https://issues.apache.org/jira/browse/FLINK-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900324#comment-14900324
 ] 

ASF GitHub Bot commented on FLINK-2622:
---------------------------------------

Github user HuangWHWHW commented on the pull request:

    https://github.com/apache/flink/pull/1098#issuecomment-141898429
  
    @tillrohrmann 
    Thanks!
    For saving the time, I usually `run mvn` verify in the sub-module where I 
changed.
    So, I forgot the DataStream.java in the other module before.
    
    And I can see the CI detail now, and is the CI error following related to 
me?
    `Tests in error: 
    
org.apache.flink.yarn.YARNSessionFIFOITCase.testJavaAPI(org.apache.flink.yarn.YARNSessionFIFOITCase)
      Run 1: YARNSessionFIFOITCase.testJavaAPI:642 ยป Runtime Unable to get 
Cluster status f...
      Run 2: 
YARNSessionFIFOITCase.checkForProhibitedLogContents:94->YarnTestBase.ensureNoProhibitedStringInLogFiles:294
 Found a file 
/home/travis/build/apache/flink/flink-yarn-tests/target/flink-yarn-tests-fifo/flink-yarn-tests-fifo-logDir-nm-1_0/application_1442651724242_0009/container_1442651724242_0009_01_000001/jobmanager-main.log
 with a prohibited string: [Exception, Started 
[email protected]:8081]
    `
    I'll try to rerun the CI and may report this error if this is not due to my 
PR.


> Scala DataStream API does not have writeAsText method which supports WriteMode
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-2622
>                 URL: https://issues.apache.org/jira/browse/FLINK-2622
>             Project: Flink
>          Issue Type: Bug
>          Components: Scala API, Streaming
>            Reporter: Till Rohrmann
>
> The Scala DataStream API, unlike the Java DataStream API, does not support a 
> {{writeAsText}} method which takes the {{WriteMode}} as a parameter. In order 
> to make the two APIs consistent, it should be added to the Scala DataStream 
> API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to