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 2017/08/21 13:47:00 UTC

[jira] [Closed] (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:all-tabpanel ]

Aljoscha Krettek closed FLINK-7477.
-----------------------------------
    Resolution: Fixed

Implemented in 0a0f6ed6c3d6cff702e4322293340274bea5e7d9

> 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
>             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
(v6.4.14#64029)