[
https://issues.apache.org/jira/browse/CALCITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122301#comment-15122301
]
Josh Elser commented on CALCITE-642:
------------------------------------
bq. I don't want to be a jerk about this
Not at all! I'm just trying to make sure I understand the scope of the
objection.
bq. The client might be used in an environment (say an app server) that has an
incompatible version of Dropwizard
Let me play with this, we might be able to work around this the same way we did
for protobuf (relocating the classes in the shaded jar). This is a bit dirtier
since it's not self-contained like protobuf was (we expect users to have some
interactions). Let me brainstorm some ideas.
> 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)
