[
https://issues.apache.org/jira/browse/IMPALA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-1716.
-----------------------------------
Resolution: Won't Do
I don't think this is a good fit for the metrics infra given the way things
have evolved. We do have a stripped-down JSON representation of the profile -
IMPALA-5149
> Move runtime profiles to metrics, JSON
> --------------------------------------
>
> Key: IMPALA-1716
> URL: https://issues.apache.org/jira/browse/IMPALA-1716
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend
> Affects Versions: Impala 2.1
> Reporter: Henry Robinson
> Assignee: Henry Robinson
> Priority: Minor
> Labels: usability
>
> With the recent changes to the metrics infrastructure, we should start to
> move the runtime profiles to be a {{MetricGroup}}, and replace the counters
> with their metric equivalents. The aim is to have metrics and runtime
> profiles have the same internal and external representation, and for runtime
> profiles to be easier to fit into the template framework.
> There are external dependencies on the Thrift data structures that represent
> runtime profiles, so we can't replace those immediately, but the best
> approach is probably a compatibility shim (this would possibly also allow us
> to retain the RPCs that send and merge runtime profiles, but we should try
> and port those over as well).
> Then we can write tools that visualise runtime profiles more easily, we can
> provide richer tooling in our debug webpages (e.g. generating tree diagrams
> for plans).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
