You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by ch...@apache.org on 2018/06/05 06:48:44 UTC

[1/2] flink git commit: [FLINK-9517][docs] Fix broken links in CLI and Upgrade docs

Repository: flink
Updated Branches:
  refs/heads/master d63b98371 -> 8372e2d3e


[FLINK-9517][docs] Fix broken links in CLI and Upgrade docs

This closes #6113.


Project: http://git-wip-us.apache.org/repos/asf/flink/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink/commit/58233ef6
Tree: http://git-wip-us.apache.org/repos/asf/flink/tree/58233ef6
Diff: http://git-wip-us.apache.org/repos/asf/flink/diff/58233ef6

Branch: refs/heads/master
Commit: 58233ef6734609a876fb8c446c18a06f3cb6f099
Parents: d63b983
Author: Yadan.JS <y_...@yahoo.com>
Authored: Mon Jun 4 07:18:24 2018 -0400
Committer: zentol <ch...@apache.org>
Committed: Tue Jun 5 08:47:26 2018 +0200

----------------------------------------------------------------------
 docs/ops/cli.md       | 2 +-
 docs/ops/upgrading.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/flink/blob/58233ef6/docs/ops/cli.md
----------------------------------------------------------------------
diff --git a/docs/ops/cli.md b/docs/ops/cli.md
index ebee426..521aced 100644
--- a/docs/ops/cli.md
+++ b/docs/ops/cli.md
@@ -148,7 +148,7 @@ This will trigger a savepoint for the job with ID `jobId`, and returns the path
 
 Furthermore, you can optionally specify a target file system directory to store the savepoint in. The directory needs to be accessible by the JobManager.
 
-If you don't specify a target directory, you need to have [configured a default directory](#configuration) (see [Savepoints]({{site.baseurl}}/ops/state/savepoints.html#configuration)). Otherwise, triggering the savepoint will fail.
+If you don't specify a target directory, you need to have [configured a default directory]({{site.baseurl}}/ops/state/savepoints.html#configuration). Otherwise, triggering the savepoint will fail.
 
 #### Trigger a Savepoint with YARN
 

http://git-wip-us.apache.org/repos/asf/flink/blob/58233ef6/docs/ops/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/ops/upgrading.md b/docs/ops/upgrading.md
index 11e469d..c9a7969 100644
--- a/docs/ops/upgrading.md
+++ b/docs/ops/upgrading.md
@@ -107,7 +107,7 @@ When upgrading an application by changing its topology, a few things need to be
 * **Adding a stateful operator:** The state of the operator will be initialized with the default state unless it takes over the state of another operator.
 * **Removing a stateful operator:** The state of the removed operator is lost unless another operator takes it over. When starting the upgraded application, you have to explicitly agree to discard the state.
 * **Changing of input and output types of operators:** When adding a new operator before or behind an operator with internal state, you have to ensure that the input or output type of the stateful operator is not modified to preserve the data type of the internal operator state (see above for details).
-* **Changing operator chaining:** Operators can be chained together for improved performance. When restoring from a savepoint taken since 1.3.x it is possible to modify chains while preserving state consistency. It is possible a break the chain such that a stateful operator is moved out of the chain. It is also possible to append or inject a new or existing stateful operator into a chain, or to modify the operator order within a chain. However, when upgrading a savepoint to 1.3.x it is paramount that the topology did not change in regards to chaining. All operators that are part of a chain should be assigned an ID as described in the [Matching Operator State](#Matching Operator State) section above.
+* **Changing operator chaining:** Operators can be chained together for improved performance. When restoring from a savepoint taken since 1.3.x it is possible to modify chains while preserving state consistency. It is possible a break the chain such that a stateful operator is moved out of the chain. It is also possible to append or inject a new or existing stateful operator into a chain, or to modify the operator order within a chain. However, when upgrading a savepoint to 1.3.x it is paramount that the topology did not change in regards to chaining. All operators that are part of a chain should be assigned an ID as described in the [Matching Operator State](#matching-operator-state) section above.
 
 ## Upgrading the Flink Framework Version
 


[2/2] flink git commit: [FLINK-9518][docs] Adjust password in SSL setup config example

Posted by ch...@apache.org.
[FLINK-9518][docs] Adjust password in SSL setup config example

This closes #6114.


Project: http://git-wip-us.apache.org/repos/asf/flink/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink/commit/8372e2d3
Tree: http://git-wip-us.apache.org/repos/asf/flink/tree/8372e2d3
Diff: http://git-wip-us.apache.org/repos/asf/flink/diff/8372e2d3

Branch: refs/heads/master
Commit: 8372e2d3e6d08cf75ddcee974156cd4126c8c22a
Parents: 58233ef
Author: Yadan.JS <y_...@yahoo.com>
Authored: Mon Jun 4 07:33:52 2018 -0400
Committer: zentol <ch...@apache.org>
Committed: Tue Jun 5 08:48:06 2018 +0200

----------------------------------------------------------------------
 docs/ops/security-ssl.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/flink/blob/8372e2d3/docs/ops/security-ssl.md
----------------------------------------------------------------------
diff --git a/docs/ops/security-ssl.md b/docs/ops/security-ssl.md
index f43d214..b70d867 100644
--- a/docs/ops/security-ssl.md
+++ b/docs/ops/security-ssl.md
@@ -79,20 +79,20 @@ Configure each node in the standalone cluster to pick up the keystore and trusts
 {% highlight yaml %}
 security.ssl.enabled: true
 security.ssl.keystore: /usr/local/node1.keystore
-security.ssl.keystore-password: abc123
-security.ssl.key-password: abc123
+security.ssl.keystore-password: password
+security.ssl.key-password: password
 security.ssl.truststore: /usr/local/ca.truststore
-security.ssl.truststore-password: abc123
+security.ssl.truststore-password: password
 {% endhighlight %}
 
 #### Node 2
 {% highlight yaml %}
 security.ssl.enabled: true
 security.ssl.keystore: /usr/local/node2.keystore
-security.ssl.keystore-password: abc123
-security.ssl.key-password: abc123
+security.ssl.keystore-password: password
+security.ssl.key-password: password
 security.ssl.truststore: /usr/local/ca.truststore
-security.ssl.truststore-password: abc123
+security.ssl.truststore-password: password
 {% endhighlight %}
 
 * Restart the flink components to enable SSL for all of flink's internal communication
@@ -109,10 +109,10 @@ The keystores and truststore should be generated and deployed on all nodes in th
 {% highlight yaml %}
 security.ssl.enabled: true
 security.ssl.keystore: /usr/local/node.keystore
-security.ssl.keystore-password: abc123
-security.ssl.key-password: abc123
+security.ssl.keystore-password: password
+security.ssl.key-password: password
 security.ssl.truststore: /usr/local/ca.truststore
-security.ssl.truststore-password: abc123
+security.ssl.truststore-password: password
 {% endhighlight %}
 
 Now you can start the YARN session from the CLI like you would normally do.