accumulo-notifications mailing list archives

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

     [ https://issues.apache.org/jira/browse/ACCUMULO-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser resolved ACCUMULO-3404.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.7.0)

Hrm, I think I've convinced myself otherwise. There were methods on Trace which is what users
were directed to use. In the specific issue I'm looking at, I should have used a reference
to the Trace class instead of the Tracer class. I'll fix this one downstream.

> 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
>
> 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