[
https://issues.apache.org/jira/browse/AMBARI-19330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802968#comment-15802968
]
Miklos Gergely commented on AMBARI-19330:
-----------------------------------------
committed to trunk:
{code:java}
commit b46a2f627e2137f2f361239f944869cf0e0dfd1d
Author: Miklos Gergely <mgerg...@hortonworks.com>
Date: Fri Jan 6 01:10:46 2017 +0100
AMBARI-19330 LogSearch upgrade support 2.4 -> 2.5
Change-Id: I1fd3ac23499eba6a96e1c3297f6895cc5b36a956
{code}
committed to branch-2.5:
{code:java}
commit 50e36c7f80b12b03106ab8277956d7999eb9b8da
Author: Miklos Gergely <mgerg...@hortonworks.com>
Date: Fri Jan 6 00:39:08 2017 +0100
AMBARI-19330 LogSearch upgrade support 2.4 -> 2.5
Change-Id: If6d7a7f94c2e858cbd7d73ad0c9440aeec89c0ab
{code}
> LogSearch upgrade support 2.4 -> 2.5
> ------------------------------------
>
> Key: AMBARI-19330
> URL: https://issues.apache.org/jira/browse/AMBARI-19330
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19330.patch
>
>
> Check configuration differences between logsearch in ambari version 2.4 and
> 2.5.
> Manually do a yum upgrade with new packages, then during ambari upgrade:
> - check the new configurations are added properly
> - implement renames/deletions in UpgradeCatalogXX.java
> additional taks here (not really related with upgrade):
> - config cleanup (check configuration dependencies, display names, typos etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
