[ 
https://issues.apache.org/jira/browse/AMBARI-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540259#comment-14540259
 ] 

Hudson commented on AMBARI-11064:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #2571 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/2571/])
AMBARI-11064 Widgets: Graph change API calls to use null padding rather than 
zero padding (graphs are misleading for recent data points as they are shown as 
zero when there's no data). (atkach) (atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=89cbc4594b91ba010934a2d8e15ad3810ac83728)
* ambari-web/test/views/common/widget/graph_widget_view_test.js
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/views/common/chart/linear_time.js
* ambari-web/app/views/common/widget/graph_widget_view.js


> Widgets: Graph change API calls to use null padding rather than zero padding 
> (graphs are misleading for recent data points as they are shown as zero when 
> there's no data)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11064
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11064
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11064.patch
>
>
> Ambari Metrics API have recently changed to automatically pad missing data 
> with zeros.
> However, this creates strange user experience where more recent data, if the 
> metrics collection is somehow lagging, to drop off to zero. This is 
> misleading.
> We should convert the API calls to use null padding and make sure to not show 
> any data in case of null (rather than zero).



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

Reply via email to