alpinegizmo commented on a change in pull request #15845:
URL: https://github.com/apache/flink/pull/15845#discussion_r627218732
##########
File path: docs/content/docs/deployment/config.md
##########
@@ -34,6 +34,8 @@ The configuration is parsed and evaluated when the Flink
processes are started.
The out of the box configuration will use your default Java installation. You
can manually set the environment variable `JAVA_HOME` or the configuration key
`env.java.home` in `conf/flink-conf.yaml` if you want to manually override the
Java runtime to use.
+You can specifiy a different configuration directory location by defining the
`FLINK_CONF_DIR` environment variable. For resource-providers which provide
non-session deployments, you can specifiy per-job configurations this way. Make
a copy of the `conf` directory from the Flink distribution and modify the
settings on a per-job basis. Note that this is not supported in Docker or
standalone Kubernetes deployments.
Review comment:
What happens if I set FLINK_CONF_DIR when submitting a job to a session
cluster?
```suggestion
You can specify a different configuration directory location by defining the
`FLINK_CONF_DIR` environment variable. For resource providers which provide
non-session deployments, you can specify per-job configurations this way. Make
a copy of the `conf` directory from the Flink distribution and modify the
settings on a per-job basis. Note that this is not supported in Docker or
standalone Kubernetes deployments.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
