[
https://issues.apache.org/jira/browse/AMBARI-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983695#comment-15983695
]
Hudson commented on AMBARI-20845:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1448 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1448/])
AMBARI-20845. Include cluster filter in every Log Search request in
(rnettleton:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2daa20e1f6f8a7101b569f0c59b8fe6f79c079bb])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImplTest.java
> Include cluster filter in every Log Search request in Ambari server
> -------------------------------------------------------------------
>
> Key: AMBARI-20845
> URL: https://issues.apache.org/jira/browse/AMBARI-20845
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.1
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.5.1
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The Ambari LogSearch integration layer should be updated to pass the name of
> the current cluster to the LogSearch Portal Server when requesting either
> Logging component metadata or when making a query request for logging data
> itself.
> In Ambari 2.5.1, the LogSearch service has been updated to potentially
> archive data from multiple clusters. The Ambari Integration layer should be
> updated to reflect this, in order to indicate to LogSearch what cluster's
> data is requested, since Ambari only will require the currently managed
> cluster's log data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
