rmetzger commented on a change in pull request #12491:
URL: https://github.com/apache/flink/pull/12491#discussion_r435742322
##########
File path: docs/ops/deployment/hadoop.md
##########
@@ -44,27 +44,16 @@ that are running Flink components.
When running on YARN, this is usually not a problem because the components
running inside YARN will be started with the Hadoop classpaths, but it can
happen that the Hadoop dependencies must be in the classpath when submitting a
-job to YARN. For this, it's usually enough to do a
+job to YARN. For this, it's usually enough to run
{% highlight bash %}
export HADOOP_CLASSPATH=`hadoop classpath`
{% endhighlight %}
-in the shell. Note that `hadoop` is the hadoop binary and that `classpath` is
an argument that will make it print the configured Hadoop classpath.
+in the shell. Note that `hadoop` is the hadoop binary and that `classpath` is
an argument that will make it print the configured Hadoop classpath. The
classpath returned by `hadoop classpath` also includes the Hadoop configuration
directories.
-Putting the Hadoop configuration in the same class path as the Hadoop
libraries makes Flink pick up that configuration.
-
-## Referencing a Hadoop configuration
-
-You can reference a Hadoop configuration by setting the environment variable
`HADOOP_CONF_DIR`.
-
-```sh
-HADOOP_CONF_DIR=/path/to/etc/hadoop
-```
-
-Referencing the HDFS configuration in the [Flink configuration]({{
site.baseurl }}/ops/config.html#hdfs) is deprecated.
-
-Another way to provide the Hadoop configuration is to have it on the class
path of the Flink process, see more details above.
+If you are manually assemling the `HADOOP_CLASSPATH` variable, we recommend
+pointing to the Hadoop configuration directory through that as well.
Review comment:
Thank you for the suggestion. I was also unhappy with the wording, but
couldn't come up with anything better.
----------------------------------------------------------------
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]
