[
https://issues.apache.org/jira/browse/AMBARI-20773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-20773:
-------------------------------
Fix Version/s: metrics-3.0.0
(was: 3.0.0)
> AMS: Schema changes for nextGen feature support
> -----------------------------------------------
>
> Key: AMBARI-20773
> URL: https://issues.apache.org/jira/browse/AMBARI-20773
> Project: Ambari
> Issue Type: Epic
> Components: ambari-metrics
> Affects Versions: metrics-3.0.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: metrics-3.0.0
>
>
> Presently, AMS stores (metricName, 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.
> This epic is used to track the investigation and implementation of 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
