[
https://issues.apache.org/jira/browse/HIVE-10761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876100#comment-14876100
]
Szehon Ho commented on HIVE-10761:
----------------------------------
1. Yes that's right it's a copy and paste error and was fixed in a subsequent
fix-up JIRA :( , I think its ok not to document all former incarnations to
reduce noise?
2. Yea I think it doesn't matter, as the the time validator is for default if
there is no unit value defined in the parameter string, as far as I know.
Thanks for the fix-up to the edit!
> Create codahale-based metrics system for Hive
> ---------------------------------------------
>
> Key: HIVE-10761
> URL: https://issues.apache.org/jira/browse/HIVE-10761
> Project: Hive
> Issue Type: New Feature
> Components: Diagnosability
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Fix For: 1.3.0, 2.0.0
>
> Attachments: HIVE-10761.2.patch, HIVE-10761.3.patch,
> HIVE-10761.4.patch, HIVE-10761.5.patch, HIVE-10761.6.patch, HIVE-10761.patch,
> hms-metrics.json
>
>
> There is a current Hive metrics system that hooks up to a JMX reporting, but
> all its measurements, models are custom.
> This is to make another metrics system that will be based on Codahale (ie
> yammer, dropwizard), which has the following advantage:
> * Well-defined metric model for frequently-needed metrics (ie JVM metrics)
> * Well-defined measurements for all metrics (ie max, mean, stddev, mean_rate,
> etc),
> * Built-in reporting frameworks like JMX, Console, Log, JSON webserver
> It is used for many projects, including several Apache projects like Oozie.
> Overall, monitoring tools should find it easier to understand these common
> metric, measurement, reporting models.
> The existing metric subsystem will be kept and can be enabled if backward
> compatibility is desired.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
