[
https://issues.apache.org/jira/browse/FLINK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369301#comment-16369301
]
Aljoscha Krettek commented on FLINK-8668:
-----------------------------------------
[~StephanEwen] The plan was to include it in the release notes because the
feature was previously undocumented and there's no obvious place to put this.
There is no central documentation about how Flink works with Hadoop so I
thought I can put a small section in the [config
doc|https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html].
Basically just: Make sure you set {{HADOOP_CLASSPATH}} on your machines if you
want Flink to pick up your Hadoop classpath.
Btw, I had this PR open: https://github.com/apache/flink/pull/4920 But by now I
think the only sane approach is to require users to ensure {{HADOOP_CLASSPATH}}
is set. A configuration script cannot do that for you. For example in cases
where you have a standalone cluster setup the script could give the appearance
of doing configuration but you still have to manually do steps to move that
configuration to all machines, which people would probably forget.
> 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)
