You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2017/05/10 17:20:04 UTC

[jira] [Assigned] (RANGER-1565) Make SOLR setup config docs consistent with code

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

Nigel Jones reassigned RANGER-1565:
-----------------------------------

    Assignee: Nigel Jones

> Make SOLR setup config docs consistent with code
> ------------------------------------------------
>
>                 Key: RANGER-1565
>                 URL: https://issues.apache.org/jira/browse/RANGER-1565
>             Project: Ranger
>          Issue Type: Bug
>          Components: audit
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>
> In the Apache ranger setup docs we have a section on Solr configuration at
> https://cwiki.apache.org/confluence/display/RANGER/Install+and+Configure+Solr+for+Ranger+Audits+-+Apache+Ranger+0.5
> In this doc it refers to setting JAVA_HOME in the install.properties file (the one in the contrib/ solr setup directory). However when I set this the ./setup.sh still failed with:
> # ./setup.sh
> Error: JAVA_HOME environment property not defined, aborting installation.
> Looking at the code it appears it does NOT pull out JAVA_HOME from the properties file at all, but relies on it being specified in the environment
> Ideally we would update the script to also source JAVA_HOME from install.properties, in which case the doc can stay as is. If we don't do this we need to update the docs accordingly. I would go with the properties file overriding the local environment, if the variable is set there.
> My proposal is to change the script. Happy to work this if it sounds ok...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)