You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2017/07/25 09:13:00 UTC

[jira] [Closed] (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:all-tabpanel ]

Chesnay Schepler closed FLINK-6940.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.2

1.3: c704adf0ddfb9d8196dd0efbb912ce544680082f
1.4: 8215f2e18b7cc44cf0bef0b560cbc757c2783b72

> 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, 1.4.0
>            Reporter: Bowen Li
>            Assignee: Bowen Li
>            Priority: Minor
>             Fix For: 1.4.0, 1.3.2
>
>
> 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)