You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2017/05/18 16:56:04 UTC

[jira] [Updated] (AMBARI-21061) Integrate Config History page with with websocket events

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

Andrii Tkach updated AMBARI-21061:
----------------------------------
    Attachment: AMBARI-21061.patch

> 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)