[
https://issues.apache.org/jira/browse/FLINK-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057845#comment-16057845
]
ASF GitHub Bot commented on FLINK-6940:
---------------------------------------
Github user bowenli86 commented on a diff in the pull request:
https://github.com/apache/flink/pull/4136#discussion_r123306543
--- Diff: docs/ops/state_backends.md ---
@@ -124,7 +124,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.
+job does not explicitly define a state backend. Besides, state backend
configured per-job will overwrite the default state backend configured in
`flink-conf.yaml`
--- End diff --
Yeah, this one works too.
How about "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."?
> 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)
