ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-21585) Remove environment variables from
Date Thu, 27 Jul 2017 11:28:02 GMT


Hadoop QA commented on AMBARI-21585:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:red}-1 core tests{color}.  The test build failed in [ambari-server|]

Console output:

This message is automatically generated.

> Remove environment variables from 
> --------------------------------------------------
>                 Key: AMBARI-21585
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Prabhjyot Singh
>            Assignee: Prabhjyot Singh
>         Attachments: AMBARI-21585_trunk_v1.patch, AMBARI-21585_trunk_v2.patch
> This is to remove three of the environment variables from;
>  - `ZEPPELIN_JAVA_OPTS` this initialises spark.executor.memory, spark.executor.instances
and spark.yarn.queue which should ideally be configured in Zeppelin's interpreter setting
to avoid confusion.
>  - `SPARK_YARN_USER_ENV` is no longer used.
>  - `PYTHONPATH` if required should be configured from Zeppelin's interpreter setting.

This message was sent by Atlassian JIRA

View raw message