[
https://issues.apache.org/jira/browse/AMBARI-20096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878063#comment-15878063
]
Olivér Szabó commented on AMBARI-20096:
---------------------------------------
committed to trunk:
{code:java}
commit 309dbd7581bb7826f80a21e046721ee30acc27fb
Author: oleewere <[email protected]>
Date: Mon Feb 20 15:17:59 2017 +0100
AMBARI-20096. Log Search: only update schema file for Solr if it has any
new fields in the local file (oleewere)
{code}
committed to branch-2.5:
{code:java}
commit b6df9244598c1edec3279e6baab89fd6b5d042e5
Author: oleewere <[email protected]>
Date: Mon Feb 20 15:17:59 2017 +0100
AMBARI-20096. Log Search: only update schema file for Solr if it has any
new fields in the local file (oleewere)
{code}
> 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)
