[
https://issues.apache.org/jira/browse/AMBARI-21061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016068#comment-16016068
]
Hadoop QA commented on AMBARI-21061:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12868792/AMBARI-21061.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11598//console
This message is automatically generated.
> Integrate Config History page with with websocket events
> --------------------------------------------------------
>
> Key: AMBARI-21061
> URL: https://issues.apache.org/jira/browse/AMBARI-21061
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 3.0.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-21061.patch
>
>
> Subscribe to /events/configs topic. Since sort and filtering is done on
> server side, on config change make we can’t just insert new config version,
> so UI will trigger a GET call for table update.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
