Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1BCEF20049E for ; Thu, 10 Aug 2017 14:32:40 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1A5A8169E1B; Thu, 10 Aug 2017 12:32:40 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 60669169E19 for ; Thu, 10 Aug 2017 14:32:39 +0200 (CEST) Received: (qmail 45127 invoked by uid 500); 10 Aug 2017 12:32:38 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 45118 invoked by uid 99); 10 Aug 2017 12:32:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2017 12:32:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2C3AA1A066E for ; Thu, 10 Aug 2017 12:32:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id iV1IBZyt8j3C for ; Thu, 10 Aug 2017 12:32:37 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 624B55FD9C for ; Thu, 10 Aug 2017 12:32:36 +0000 (UTC) Received: (qmail 45113 invoked by uid 99); 10 Aug 2017 12:32:35 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2017 12:32:35 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id DCDABE96B4; Thu, 10 Aug 2017 12:32:34 +0000 (UTC) From: aljoscha To: issues@flink.incubator.apache.org Reply-To: issues@flink.incubator.apache.org References: In-Reply-To: Subject: [GitHub] flink pull request #4511: [FLINK-7396] Don't put multiple directories in HAD... Content-Type: text/plain Message-Id: <20170810123234.DCDABE96B4@git1-us-west.apache.org> Date: Thu, 10 Aug 2017 12:32:34 +0000 (UTC) archived-at: Thu, 10 Aug 2017 12:32:40 -0000 Github user aljoscha commented on a diff in the pull request: https://github.com/apache/flink/pull/4511#discussion_r132439899 --- Diff: flink-dist/src/main/flink-bin/bin/config.sh --- @@ -336,16 +336,18 @@ if [ -z "${JVM_ARGS}" ]; then JVM_ARGS="" fi -# Check if deprecated HADOOP_HOME is set. -if [ -n "$HADOOP_HOME" ]; then - # HADOOP_HOME is set. Check if its a Hadoop 1.x or 2.x HADOOP_HOME path - if [ -d "$HADOOP_HOME/conf" ]; then - # its a Hadoop 1.x - HADOOP_CONF_DIR="$HADOOP_CONF_DIR:$HADOOP_HOME/conf" - fi - if [ -d "$HADOOP_HOME/etc/hadoop" ]; then - # Its Hadoop 2.2+ - HADOOP_CONF_DIR="$HADOOP_CONF_DIR:$HADOOP_HOME/etc/hadoop" +# Check if deprecated HADOOP_HOME is set, and specify config path to HADOOP_CONF_DIR if it's empty. +if [ -z "$HADOOP_CONF_DIR" ]; then + if [ -n "$HADOOP_HOME" ]; then + # HADOOP_HOME is set. Check if its a Hadoop 1.x or 2.x HADOOP_HOME path + if [ -d "$HADOOP_HOME/conf" ]; then + # its a Hadoop 1.x + HADOOP_CONF_DIR="$HADOOP_CONF_DIR:$HADOOP_HOME/conf" --- End diff -- This is still putting multiple colon-separated directories in `HADOOP_CONF_DIR`. Simply removing `$HADOOP_CONF_DIR:` here should work. Same below. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---