Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/5531#discussion_r169606158
--- Diff: docs/ops/deployment/hadoop.md ---
@@ -0,0 +1,47 @@
+---
+title: "Hadoop Integration"
+nav-title: Hadoop Integration
+nav-parent_id: deployment
+nav-pos: 8
+---
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+* This will be replaced by the TOC
+{:toc}
+
+## Configuring Flink with Hadoop Classpaths
+
+Flink will use the environment variable `HADOOP_CLASSPATH` to augment the
+classpath that is used when starting Flink components such as the Client,
+JobManager, or TaskManager. Most Hadoop distributions and cloud
environments
+will not set this variable by default so if the Hadoop classpath should be
+picked up by Flink the environment variable must be exported on all
machines
+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
+
+```
+export HADOOP_CLASSPATH=`hadoop classpath`
--- End diff --
it's the `hadoop` binary with `classpath` as argument
---
