[ 
https://issues.apache.org/jira/browse/AMBARI-17902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396287#comment-15396287
 ] 

Jayush Luniya commented on AMBARI-17902:
----------------------------------------

Branch-2.4
commit 417fb113e2882da6aac0cb8567e10b2fdb8272db
Author: Jayush Luniya <jlun...@hortonworks.com>
Date:   Wed Jul 27 13:20:56 2016 -0700

    AMBARI-17902: Config changes to support external solr and internal solr for 
Ranger (Mugdha Varadkar via jluniya)

> Config changes to support external solr and internal solr for Ranger
> --------------------------------------------------------------------
>
>                 Key: AMBARI-17902
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17902
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17902.1.patch, AMBARI-17902.patch
>
>
> Ranger Service needs to support the following two scenarios in case when 
> audit to solr is enabled and solrCloud is used as destination.
> External Solr
> * If Audit to Solr is Enabled and Solr Cloud == true and Kerberos is Enabled
> ** If is_external_solr == true
> *** If is_external_solr_kerberized == true
> Then recommend ranger.is.solr.kerberised as true.
> Ambari Internal Solr
> * If Audit to Solr is Enabled and Solr Cloud == true
> ** If is_external_solr == false and Kerberos is Enabled
> Then directly recommend ranger.is.solr.kerberised as true.



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

Reply via email to