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 2016/05/12 13:26:15 UTC

[jira] [Updated] (AMBARI-16446) Ranger audit properties should be configured to use Ambari installed Solr (LogSearch)

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

Mugdha Varadkar updated AMBARI-16446:
-------------------------------------
    Attachment: AMBARI-16446.patch

> Ranger audit properties should be configured to use Ambari installed Solr (LogSearch)
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-16446
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16446
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16446.patch
>
>
> – By Default, turn on Audit to Solr
> – Provided Ambari installed Solr instance (from LogSearch) is available, populate Ranger Audit properties with that Solr instance
> – During upgrade scenarios, if user has already configured Solr properties (with Solr instance outside Ambari), those values need to be preserved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)