[
https://issues.apache.org/jira/browse/CALCITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122298#comment-15122298
]
Julian Hyde commented on CALCITE-642:
-------------------------------------
The problem with dependencies is not just code size. The client might be used
in an environment (say an app server) that has an incompatible version of
Dropwizard. Same reason that Avatica does not depend on Guava.
Deal breaker? I don't know. I don't want to be a jerk about this. But keeping
the architecture simple might be worth being a jerk about. Can it be an
optional dependency?
> 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)
