[
https://issues.apache.org/jira/browse/AMBARI-15070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151159#comment-15151159
]
Hudson commented on AMBARI-15070:
---------------------------------
ABORTED: Integrated in Ambari-branch-2.2 #350 (See
[https://builds.apache.org/job/Ambari-branch-2.2/350/])
AMBARI-15070. Graph scale behaviour is incorrect if time range is (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4c73a51dc42c243ff100869d323042e75c7f6431])
* ambari-web/test/mixins/common/widget_mixin_test.js
* ambari-web/app/views/common/chart/linear_time.js
* ambari-web/test/views/common/chart/linear_time_test.js
* ambari-web/app/mixins/common/widgets/widget_mixin.js
* ambari-web/app/views/main/admin/stack_upgrade/versions_view.js
* ambari-web/test/utils/ajax/ajax_test.js
* ambari-web/app/utils/ajax/ajax.js
> Graph scale behaviour is incorrect if time range is switched before graph
> data API call is complete
> ---------------------------------------------------------------------------------------------------
>
> Key: AMBARI-15070
> URL: https://issues.apache.org/jira/browse/AMBARI-15070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.2
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15070_222.patch, AMBARI-15070_trunk.patch
>
>
> *STR*
> # Switch metrics time range from 'Last 1 hour' to 'Last 1 year' (for example,
> on Dashboard; data for 1 year should be available).
> # While metrics API call is pending, switch time range back to 1 hour (can be
> reproduced if connection rate is low or server is highly loaded so that
> requests are being processed slowly).
> *Result*
> After request with data for last year is complete, it's displayed on the
> graph, but the scale is rendered with an accuracy to 1 hour which makes graph
> unusable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
