[
https://issues.apache.org/jira/browse/AMBARI-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520247#comment-14520247
]
Hudson commented on AMBARI-10809:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #2477 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2477/])
AMBARI-10809. AMS: navigating graph time ranges are not correct. (swagle)
(swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7f753b4448e4b370c100d663e8a4f4fd1f0ec5b0)
*
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/MetricsPaddingMethodTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPaddingMethod.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProvider.java
> AMS: navigating graph time ranges are not correct
> -------------------------------------------------
>
> Key: AMBARI-10809
> URL: https://issues.apache.org/jira/browse/AMBARI-10809
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.1.0
>
>
> Graphs are not padding time for full range. For example: view 4 hours with a
> cluster is only a few hours old. The graphs don't change even thought the
> APIs calls are being made. The API should return padded 0 values (or the
> graph needs to display the full range).
> Keep the existing API behavior of padding with zeros for missing data points
> so that this has zero impact on the UI or any other third-party code using
> the Ambari metrics API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
