You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2018/02/16 08:57:00 UTC

[jira] [Commented] (FLINK-7477) Use "hadoop classpath" to augment classpath when available

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

Aljoscha Krettek commented on FLINK-7477:
-----------------------------------------

[~kkrugler] I added this code but now I would be in favour of just removing it, along with the code that uses {{hbase classpath}}. 

Out of curiosity, are you running on YARN? Shouldn't this also include the Hadoop dependencies in your classpath anyways when executing the TaskManagers on YARN?

> Use "hadoop classpath" to augment classpath when available
> ----------------------------------------------------------
>
>                 Key: FLINK-7477
>                 URL: https://issues.apache.org/jira/browse/FLINK-7477
>             Project: Flink
>          Issue Type: Bug
>          Components: Startup Shell Scripts
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>             Fix For: 1.4.0
>
>
> Currently, some cloud environments don't properly put the Hadoop jars into {{HADOOP_CLASSPATH}} (or don't set {{HADOOP_CLASSPATH}}) at all. We should check in {{config.sh}} if the {{hadoop}} binary is on the path and augment our {{INTERNAL_HADOOP_CLASSPATHS}} with the result of {{hadoop classpath}} in our scripts.
> This will improve the out-of-box experience of users that otherwise have to manually set {{HADOOP_CLASSPATH}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)