[jira] [Resolved] (IMPALA-7817) impala_config.sh appends to various env variables

["Joe McDonnell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe McDonnell resolved IMPALA-7817.
-----------------------------------
    Fix Version/s: Impala 3.3.0
       Resolution: Fixed

There are still some environment variable calculations that are not idempotent, but the classpath issue is substantially improved by this commit:

[https://github.com/apache/impala/commit/559f19a5be95d686a71e616517ad4ae916c85824]

We are generating the CLASSPATH by reading a file generated by the maven build, so it won't just put everything on the CLASSPATH. 

> impala_config.sh appends to various env variables
> -------------------------------------------------
>
>                 Key: IMPALA-7817
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7817
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 3.0
>            Reporter: Michal Ostrowski
>            Priority: Major
>             Fix For: Impala 3.3.0
>
>
> If one repeatedly sources "bin/impala_config.sh", the script does not "set" environment variables, it frequently appends to them.  If one sources hits files repeatedly variables such as CLASSPATH keep growing and growing.
> This is maybe a nuisance if CDH_BUILD_NUMBER hasn't changed, but if it has changed then the results can be unpredictable – because the resulting CLASSPATH will have the old CDH build number path included as well as the new one.
> The proper solution (other than not depending on environment variables as much) is to write an "undo.sh" file of some sort that can be used to undo what impala_config.sh does.  Subsequently impala_config.sh can run an undo.sh to clean an environment before setting up a new one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)