[
https://issues.apache.org/jira/browse/CALCITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122381#comment-15122381
]
Josh Elser commented on CALCITE-642:
------------------------------------
So this is what I'm thinking:
* Remove all dropwizard API use in Avatica directly, create my own interfaces
ala "avatica-metrics"
* Implement interfaces in an "avatica-metrics-dropwizard-3" (or something --
need to figure out what/if-at-all is their compat statement)
* Have calcite-avatica create two (shaded) artifacts: "calcite-avatica.jar" and
"calcite-avatica-without-metrics.jar" (could also do a with-metrics instead of
without-metrics but I'm being selfish and hoping the without-metrics jar would
be less common)
For those running in an AppServer (or some shared environment w/o classpath
isolation), they can use the without-metrics jar and provide the version they
want. We would also be able to provide bindings for other systems natively (if
necessary). Hopefully, the common case would still be the single
calcite-avatica.jar, but we wouldn't screw over those whose needs aren't
satisfied.
> Avatica server metrics
> ----------------------
>
> Key: CALCITE-642
> URL: https://issues.apache.org/jira/browse/CALCITE-642
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Nick Dimiduk
> Assignee: Josh Elser
> 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)
