You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Mugdha Varadkar (JIRA)" <ji...@apache.org> on 2018/08/10 09:33:00 UTC

[jira] [Reopened] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger

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

Mugdha Varadkar reopened AMBARI-22951:
--------------------------------------

Reopening the jira to provide the fix in trunk and branch-2.7

> Export JAVA_HOME env variable in shell script for Ranger
> --------------------------------------------------------
>
>                 Key: AMBARI-22951
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22951
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.6.2
>
>         Attachments: AMBARI-22951.patch
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Need to export JAVA_HOME variable in ranger-admin-env.sh, so that [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] knows which java to be used for processing.



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