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

Posted to issues@ambari.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2016/05/25 04:37:12 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15299440#comment-15299440 ] 

Gautam Borad commented on AMBARI-16446:
---------------------------------------

Committed to trunk : https://github.com/apache/ambari/commit/b81fd1f60c0cdc74caf95861e2652dd355810956
Committed to branch-2.4 : https://github.com/apache/ambari/commit/cf725e1cd334b81151e0ff9e00ca896e513f7986 

> 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.1.patch, AMBARI-16446.2.patch, 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)