flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sachingoel0101 <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-2797][cli] Add support for running jobs...
Date Wed, 11 Nov 2015 09:41:07 GMT
Github user sachingoel0101 commented on the pull request:

    https://github.com/apache/flink/pull/1214#issuecomment-155717073
  
    @mxm , fortunately, this time I was able to run the tests on my machine. :)
    I'm seeing a strange error. This is the error in Task manager log file for per job detached
streaming test:
    ```java
    java.io.IOException: File or directory already exists. Existing files and directories
are not overwritten in NO_OVERWRITE mode. Use OVERWRITE mode to overwrite existing files and
directories.
    	at org.apache.flink.core.fs.FileSystem.initOutPathLocalFS(FileSystem.java:549)
    	at org.apache.flink.api.common.io.FileOutputFormat.open(FileOutputFormat.java:226)
    	at org.apache.flink.api.java.io.TextOutputFormat.open(TextOutputFormat.java:77)
    	at org.apache.flink.streaming.api.functions.sink.FileSinkFunction.open(FileSinkFunction.java:62)
    	at org.apache.flink.api.common.functions.util.FunctionUtils.openFunction(FunctionUtils.java:36)
    	at org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.open(AbstractUdfStreamOperator.java:89)
    	at org.apache.flink.streaming.runtime.tasks.StreamTask.openAllOperators(StreamTask.java:286)
    	at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:213)
    	at org.apache.flink.runtime.taskmanager.Task.run(Task.java:584)
    	at java.lang.Thread.run(Thread.java:745)
    ```
    
    This is surprising because I have made no changes to the way file writes or overwrites
are handled. 
    Here's the thing though: it should fail, because the folder is created at line 475 in
`YarnSessionFIFOITCase` and the program will need to overwrite it.
    ```java
    File tmpOutFolder = null;
    try{
    	tmpOutFolder = tmp.newFolder();
    }
    catch(IOException e) {
    	throw new RuntimeException(e);
    }
    ```
    But the tests always pass on the master branch. 
    The rest of the tests which follow this automatically fail because they again check all
the logs files for exception strings.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message