ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-16129) LogSearch Integration using incorrect query parameters for LogSearch
Date Wed, 27 Apr 2016 15:41:13 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-16129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Nettleton updated AMBARI-16129:
--------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Patch merged to trunk


> LogSearch Integration using incorrect query parameters for LogSearch
> --------------------------------------------------------------------
>
>                 Key: AMBARI-16129
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16129
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16129.patch.2
>
>
> The LogSearch integration layer in Ambari is passing incorrect query parameters to the
LogSearch Server.  Recent multi-node testing has uncovered this issue. 
> The LogSearch integration code should use "host_name" for specifying hosts in query URLs,
and "component_name" for specifying the component for a given LogSearch query.  The "component_name"
change is related to a change in the parameters for LogSearch itself, which used to use "components_name".
 
> The integration code should be updated to use these query parameter names.  
> I'm working on a fix for this, and will be submitting a patch shortly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message