flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aljoscha <...@git.apache.org>
Subject [GitHub] flink pull request #5486: [FLINK-8600] Don't use flaky truncate() test in Bu...
Date Wed, 14 Feb 2018 13:52:13 GMT
GitHub user aljoscha opened a pull request:


    [FLINK-8600] Don't use flaky truncate() test in BucketingSink

    R: @kl0u 

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

    $ git pull https://github.com/aljoscha/flink jira-8600-bucketing-sink-truncate

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


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

    This closes #5486
commit 4ca30f33f297d66ae5008226eb5d80936e68d887
Author: Aljoscha Krettek <aljoscha.krettek@...>
Date:   2018-02-14T13:48:22Z

    [FLINK-8600] Don't use flaky truncate() test in BucketingSink
    The test was failing when using PrestoS3FileSystem because it doesn't
    use an absolute/qualified path. The test was questionable anyways
    because it tries writing to a random path that might not be writable by
    the user.
    This replaces the check with an explicit configuration setting for
    enabling/disabling truncate() support.



View raw message