[
https://issues.apache.org/jira/browse/FLINK-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080230#comment-16080230
]
ASF GitHub Bot commented on FLINK-6940:
---------------------------------------
Github user zentol commented on a diff in the pull request:
https://github.com/apache/flink/pull/4136#discussion_r126401914
--- Diff: docs/ops/state_backends.md ---
@@ -123,8 +123,7 @@ RocksDBStateBackend is currently the only backend that
offers incremental checkp
## Configuring a State Backend
-State backends can be configured per job. In addition, you can define a
default state backend to be used when the
-job does not explicitly define a state backend.
+State backends can be configured per job in code. In addition, you can
define a default state backend in **flink-conf.yaml** that is used when the job
does not explicitly define a state backend.
--- End diff --
huh...i just noticed the 2 subsections below that describe how to configure
the default/per-job state backend. Aren't we just duplicating details here?
@alpinegizmo Do you have any input?
> 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)
