flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wosin <...@git.apache.org>
Subject [GitHub] flink pull request #6322: [FLINK-9575]: Remove job-related BLOBS only if the...
Date Thu, 12 Jul 2018 09:31:01 GMT
GitHub user Wosin opened a pull request:


    [FLINK-9575]: Remove job-related BLOBS only if the job was removed suceā€¦

    ## What is the purpose of the change
    Currently flink removes all blobs connected with the job, no matter if the job itself
was removed successfully. This is not the desired behavior.
    ## Brief change log
    - Blobs and data will be removed only if the job itself will be removed sucessfully
    ## Verifying this change
    This change is a trivial rework / code cleanup without any test coverage.
    ## 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: yes
      - 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/Wosin/flink FLINK-9575

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 #6322
commit 1c5febebd7045e61862118649a11a85a1917a54a
Author: Wosin <blind.van@...>
Date:   2018-07-04T08:27:54Z

    FLINK-9575: Remove job-related BLOBS only if the job was removed sucessfully



View raw message