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

Posted to issues@ambari.apache.org by "Aravindan Vijayan (JIRA)" <ji...@apache.org> on 2017/06/09 17:30:19 UTC

[jira] [Created] (AMBARI-21214) Use a uuid vs long row key for metrics in AMS schema

Aravindan Vijayan created AMBARI-21214:
------------------------------------------

             Summary: Use a uuid vs long row key for metrics in AMS schema
                 Key: AMBARI-21214
                 URL: https://issues.apache.org/jira/browse/AMBARI-21214
             Project: Ambari
          Issue Type: Bug
          Components: ambari-metrics
    Affects Versions: 3.0.0
            Reporter: Aravindan Vijayan
            Assignee: Aravindan Vijayan
             Fix For: 3.0.0


Presently we store (metircName, hostname, serverTime, appId, instanceId) for every row.
Although this makes SQL query easy to write, it adds duplication when storing it in the Regions memory.
We should have a unique integer ID for an application-instance metric on a host and use that as a lookup table with a write through cache when inserting or reading data in the METRIC_RECORD table.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)