[ 
https://issues.apache.org/jira/browse/FLINK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369869#comment-16369869
 ] 

ASF GitHub Bot commented on FLINK-8668:
---------------------------------------

GitHub user aljoscha opened a pull request:

    https://github.com/apache/flink/pull/5531

    [FLINK-8668] Document how to set HADOOP_CLASSPATH for Flink

    R: @zentol @StephanEwen 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aljoscha/flink jira-8668-doc-hadoop-classpath

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5531.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5531
    
----
commit 10f6a53bcd85da126746a8cdeec97cce31c013f0
Author: Aljoscha Krettek <aljoscha.krettek@...>
Date:   2018-02-20T09:51:27Z

    [FLINK-8668] Document how to set HADOOP_CLASSPATH for Flink

----


> 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)

Reply via email to