[
https://issues.apache.org/jira/browse/CALCITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14488032#comment-14488032
]
Nick Dimiduk commented on CALCITE-642:
--------------------------------------
Yes, I looked into this a bit over the weekend. I think it's doable, though
probably a lot of code. Since I see no reason to add to Calcite a dependency on
hadoop-common (I think this is where the metrics subsystem lives), I'm thinking
we should wire up Avatica with Dropwizard metrics. I think the adaptor from
drop wizard to hadoop metrics can live over in HBase code (or maybe push down
to Hadoop), and Phoenix's wrapper around Avatica pieces can pull in the
dependency and handle wiring up the translation from one system to the other.
That'll be a bigger project, probably not until HBase 1.2 or later (or Hadoop
2.8 or later). Meanwhile, I think it's safe introduce the drop wizard dep here.
Agreed?
> Avatica server metrics
> ----------------------
>
> Key: CALCITE-642
> URL: https://issues.apache.org/jira/browse/CALCITE-642
> Project: Calcite
> Issue Type: Improvement
> Reporter: Nick Dimiduk
> Assignee: Julian Hyde
> Labels: avatica
> Fix For: next
>
>
> Along the same lines as CALCITE-641, avatica server should track some basic
> metrics. We can expose them through a "standard" API (such as Hadoop metrics,
> or Dropwizard metrics), and include them on some interval in the service log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
