[
https://issues.apache.org/jira/browse/AMBARI-21863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149121#comment-16149121
]
Hadoop QA commented on AMBARI-21863:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884682/AMBARI-21863.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12125//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12125//console
This message is automatically generated.
> Ranger should handle external Solr properly
> -------------------------------------------
>
> Key: AMBARI-21863
> URL: https://issues.apache.org/jira/browse/AMBARI-21863
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
> Affects Versions: 2.6.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.6.0
>
> Attachments: AMBARI-21863.patch
>
>
> Ranger tries to create it's configurations using the local ambari-infra Solr
> even if it is specified to use an external one.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
