[
https://issues.apache.org/jira/browse/FLINK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369945#comment-16369945
]
ASF GitHub Bot commented on FLINK-8668:
---------------------------------------
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/5531#discussion_r169287038
--- Diff: docs/ops/config.md ---
@@ -82,6 +82,26 @@ prefix that is checked against the fully qualified class
name. By default, this
If you want to change this setting you have to make sure to also include
the default patterns in
your list of patterns if you want to keep that default behaviour.
+## 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 should 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 anyways but
it
--- End diff --
fixing
> Remove "hadoop classpath" from config.sh
> ----------------------------------------
>
> Key: FLINK-8668
> URL: https://issues.apache.org/jira/browse/FLINK-8668
> Project: Flink
> Issue Type: New Feature
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Major
> Fix For: 1.5.0
>
>
> Automatically adding this when available can lead to dependency problems for
> some users and there is no way of turning of this "feature". It was added to
> make using Flink on AWS/EMR and GCE a bit easier but I think it's causing
> more harm than good.
> If users want to to augment the classpath they can always {{export
> HADOOP_CLASSPATH=...}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
