This is an automated email from the ASF dual-hosted git repository.
rmetzger pushed a commit to branch release-1.13
in repository https://gitbox.apache.org/repos/asf/flink.git
commit b389e3f446e020dcc59294204c83d88adaba26c7
Author: Robert Metzger <rmetz...@apache.org>
AuthorDate: Thu Jun 17 08:08:25 2021 +0200
[hotfix][docs] Mention -D argument for CLI
---
docs/content.zh/docs/deployment/cli.md | 8 ++++++++
docs/content/docs/deployment/cli.md | 8 ++++++++
2 files changed, 16 insertions(+)
diff --git a/docs/content.zh/docs/deployment/cli.md
b/docs/content.zh/docs/deployment/cli.md
index 13d8bb60..cd43d00 100644
--- a/docs/content.zh/docs/deployment/cli.md
+++ b/docs/content.zh/docs/deployment/cli.md
@@ -80,6 +80,14 @@ There is another action called `run-application` available
to run the job in
[Application Mode]({{< ref "docs/deployment/overview" >}}#application-mode).
This documentation does not address
this action individually as it works similarly to the `run` action in terms of
the CLI frontend.
+The `run` and `run-application` commands support passing additional
configuration parameters via the
+`-D` argument. For example setting the [maximum parallelism]({{< ref
"docs/deployment/config#pipeline-max-parallelism" >}}#application-mode)
+for a job can be done by setting `-Dpipeline.max-parallelism=120`. This
argument is very useful for
+configuring per-job or application mode clusters, because you can pass any
configuration parameter
+to the cluster, without changing the configuration file.
+
+When submitting a job to an existing session cluster, only [execution
configuration parameters]({{< ref "docs/deployment/config#execution" >}}) are
supported.
+
### Job Monitoring
You can monitor any running jobs using the `list` action:
diff --git a/docs/content/docs/deployment/cli.md
b/docs/content/docs/deployment/cli.md
index 9761288..f229367 100644
--- a/docs/content/docs/deployment/cli.md
+++ b/docs/content/docs/deployment/cli.md
@@ -78,6 +78,14 @@ There is another action called `run-application` available
to run the job in
[Application Mode]({{< ref "docs/deployment/overview" >}}#application-mode).
This documentation does not address
this action individually as it works similarly to the `run` action in terms of
the CLI frontend.
+The `run` and `run-application` commands support passing additional
configuration parameters via the
+`-D` argument. For example setting the [maximum parallelism]({{< ref
"docs/deployment/config#pipeline-max-parallelism" >}}#application-mode)
+for a job can be done by setting `-Dpipeline.max-parallelism=120`. This
argument is very useful for
+configuring per-job or application mode clusters, because you can pass any
configuration parameter
+to the cluster, without changing the configuration file.
+
+When submitting a job to an existing session cluster, only [execution
configuration parameters]({{< ref "docs/deployment/config#execution" >}}) are
supported.
+
### Job Monitoring
You can monitor any running jobs using the `list` action:
