Modify HOpTimer to support different lifecycle monitors

[ezbz]

Add tagName parameter to the start method to support other monitor lifecycle patterns such as the one mandated by Metrics (http://metrics.codahale.com/).

[patricioe]

+1 for coda hale.

Should we make the time unit in millis rather than nanos? Nanoseconds is
best where you are timing local computations.
On Sep 2, 2012 5:15 AM, "Erez Mazor" notifications@github.com wrote:

Add tagName parameter to the start method to support other monitor
lifecycle patterns such as the one mandated by Metrics (

http://metrics.codahale.com/).

You can merge this Pull Request by running:

git pull https://github.com/erezmazor/hector master

Or view, comment on, or merge it at:

#515
Commit Summary

• added HOpTimer implementation for metrics (
  https://github.com/codahal… https://github.com/codahale/metrics

File Changes

• M core/pom.xml (4)
• _M_core/src/main/java/me/prettyprint/cassandra/connection/HConnectionManager.java
  (2)
• _M_core/src/main/java/me/prettyprint/cassandra/connection/HOpTimer.java (2)
• _A_core/src/main/java/me/prettyprint/cassandra/connection/MetricsOpTimer.java
  (46)
• _M_core/src/main/java/me/prettyprint/cassandra/connection/NullOpTimer.java (2)
• _M_core/src/main/java/me/prettyprint/cassandra/connection/SpeedForJOpTimer.java
  (2)
• M pom.xml (5)

Patch Links

• https://github.com/hector-client/hector/pull/515.patch

• https://github.com/hector-client/hector/pull/515.diff

  —
  Reply to this email directly or view it on GitHubhttps://github.com/Modify HOpTimer to support different lifecycle monitors #515.

[ezbz]

Rebased with current master and added example test showing basic usage with MetricsRegistry

[zznate]

Nice! Thanks.