You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/18 07:20:02 UTC

[jira] [Commented] (FLINK-6940) Clarify the effect of configuring per-job state backend

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

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

GitHub user bowenli86 opened a pull request:

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

    [FLINK-6940][docs] Clarify the effect of configuring per-job state backend

    The documentation of having different options configuring flink state backend is confusing. We should add explicit doc explaining configuring a per-job flink state backend in code will overwrite any default state backend configured in flink-conf.yaml
    
    
    
    
    Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
    If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the [How To Contribute guide](http://flink.apache.org/how-to-contribute.html).
    In addition to going through the list, please provide a meaningful description of your changes.
    
    - [x] General
      - The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
      - The pull request addresses only one issue
      - Each commit in the PR has a meaningful commit message (including the JIRA id)
    
    - [x] Documentation
      - Documentation has been added for new functionality
      -Old documentation affected by the pull request has been updated
      - JavaDoc for public methods has been added
    
    - [x] Tests & Build
      - Functionality added by the pull request is covered by tests
      - `mvn clean verify` has been executed successfully locally or a Travis build has passed


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

    $ git pull https://github.com/bowenli86/flink FLINK-6940

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

    https://github.com/apache/flink/pull/4136.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 #4136
    
----
commit 6ef758bfc8ef44a1ed6061ce85af849cc3f65c96
Author: Bowen Li <bo...@gmail.com>
Date:   2017-06-18T07:17:20Z

    [FLINK-6940][docs] Clarify the effect of configuring per-job state backend

----


> Clarify the effect of configuring per-job state backend 
> --------------------------------------------------------
>
>                 Key: FLINK-6940
>                 URL: https://issues.apache.org/jira/browse/FLINK-6940
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.3.0
>            Reporter: Bowen Li
>            Assignee: Bowen Li
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The documentation of having different options configuring flink state backend is confusing. We should add explicit doc explaining configuring a per-job flink state backend in code will overwrite any default state backend configured in flink-conf.yaml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)