accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3404) Reinstitute a Tracer class in trace/
Date Thu, 11 Dec 2014 23:42:14 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243368#comment-14243368
] 

Christopher Tubbs commented on ACCUMULO-3404:
---------------------------------------------

Was that class instrumentation or the tracer service? If it's instrumentation, maybe it makes
sense to keep deprecated even if it's not part of the public API, but if it's part of the
tracer service, it should be safe to leave out.

However, I'd rather we stick to our definitions going forward, and the public API does not
define trace as part of it.

> Reinstitute a Tracer class in trace/
> ------------------------------------
>
>                 Key: ACCUMULO-3404
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3404
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: trace
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> o.a.a.t.i.Tracer in the trace module was removed as a part of the HTrace changes because
it is no longer needed. It would be nice to reintroduce the class, deprecate it, and make
a pointer to the new classes to use.
> This is another awkward scenario because users could have very easily considered this
class "public API" but it does not currently fit into our definition of it.
> This also has caused a breakage downstream and would be easier to fix here than all other
projects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message