GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/6244

    [FLINK-9622] Do not swallow exceptions in FileUtils#copy

    ## What is the purpose of the change
    
    This commit lets `IOExceptions` originating from `FileUtil#copy` bubble up 
instead of swallowing them.
    
    This PR is based on #6243.
    
    ## Verifying this change
    
    - Trivial fix
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
      - The serializers: (no)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
      - The S3 file system connector: (no)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (no)
      - If yes, how is the feature documented? (not applicable)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink 
cleanUpDistributedCacheDfsTest

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/6244.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #6244
    
----
commit 1ba98b2dbd2f91c815761d3b2e382a78230d021e
Author: Till Rohrmann <trohrmann@...>
Date:   2018-07-02T15:44:52Z

    [FLINK-9622] Do not swallow exceptions in FileUtils#copy

commit 82cd571b12f15fc99293173502d21370802aea55
Author: Till Rohrmann <trohrmann@...>
Date:   2018-07-03T11:36:33Z

    [FLINK-9707] Support concurrent directory creations in LocalFileSystem
    
    Support concurrent directory creations by accepting directories which have 
been
    created by a different thread/process in LocalFileSystem#mkdirs.

----


---

Reply via email to