Hadoop Integration

Referencing a Hadoop configuration

You can reference a Hadoop configuration by setting the environment variable HADOOP_CONF_DIR.


Referencing the HDFS configuration in the Flink configuration is deprecated.

Another way to provide the Hadoop configuration is to have it on the class path of the Flink process, see more details below.

Adding Hadoop Classpaths

The required classes to use Hadoop should be available in the lib/ folder of the Flink installation (on all machines running Flink) unless Flink is built with Hadoop shaded dependencies.

If putting the files into the directory is not possible, Flink also respects the HADOOP_CLASSPATH environment variable to add Hadoop jar files to the classpath.

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`

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.

Putting the Hadoop configuration in the same class path as the Hadoop libraries makes Flink pick up that configuration.

Running a job locally

To run a job locally as one JVM process using the mini cluster, the required hadoop dependencies have to be explicitly added to the classpath of the started JVM process.

To run an application using maven (also from IDE as a maven project), the required hadoop dependencies can be added as provided to the pom.xml, e.g.:


This way it should work both in local and cluster run where the provided dependencies are added elsewhere as described before.

To run or debug an application in IntelliJ Idea the provided dependencies can be included to the class path in the “Run|Edit Configurations” window.

Back to top