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/07/07 20:43:00 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=16078653#comment-16078653 ]
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_r126240877
--- 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 --
@zentol any suggestions?
> 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)