[
https://issues.apache.org/jira/browse/AMBARI-20096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878135#comment-15878135
]
Hudson commented on AMBARI-20096:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1058 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1058/])
AMBARI-20096. Log Search: only update schema file for Solr if it has any
(oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b6df9244598c1edec3279e6baab89fd6b5d042e5])
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/handler/UploadConfigurationHandler.java
> Log Search: only update schema file for Solr if it has any new fields in the
> local file
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-20096
> URL: https://issues.apache.org/jira/browse/AMBARI-20096
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.5.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-20096.patch
>
>
> Currently we upload the managed-schema file (for collections: history,
> service logs, audit logs) to zookeeper in case of the local file content
> differs from the zookeeper one. Because Solr itself can edit the file, that
> is a wrong solution. Instead of the we will check is there any new nodes in
> the local xml file. (if there is any, we will upload that to zookeeper)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
