You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/01/12 15:34:34 UTC

[jira] [Reopened] (AMBARI-8973) Add precision option support to Ambari Metrics API

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

Dmytro Sen reopened AMBARI-8973:
--------------------------------

Reverted patch due to exception messages in logs
{noformat}
"exception":"BadRequestException","message":"java.lang.Exception: precision should be seconds, minutes or hours","javaClassName":"org.apache.hadoop.yarn.webapp.BadRequestException"
{noformat}

> Add precision option support to Ambari Metrics API
> --------------------------------------------------
>
>                 Key: AMBARI-8973
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8973
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 2.0.0
>
>
> Modify AMS API layer to switch precision level based on query window.
> E.g.: Any query > 1 hour should get data from the 5 minute aggregate table unless user provides a precision parameter.
> -startTime - endTime = 1 day OR precision = minutes
> implies query => 5 minute table
> -startTime - endTime = 3 hours and precision = seconds
> implies query => minute table (METRIC_RECORD)
> So, effectively we are just using the precision as guidance paramete



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