You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/10/14 02:45:05 UTC
[jira] [Updated] (HTRACE-261) 5.0 API improvements
[ https://issues.apache.org/jira/browse/HTRACE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin Patrick McCabe updated HTRACE-261:
----------------------------------------
Component/s: core
api
> 5.0 API improvements
> --------------------
>
> Key: HTRACE-261
> URL: https://issues.apache.org/jira/browse/HTRACE-261
> Project: HTrace
> Issue Type: Improvement
> Components: api, core
> Affects Versions: 4.0
> Reporter: stack
>
> The 4.0.0 is much better than 3.x API but a few holes. Here is an umbrella issue to keep track of API improvements to do for htrace 5.0
> detach and reattach should return this. Ditto on the annotations.
> curThreadTracer should be currentThreadTracer or getCurrentThreadTracer
> Have to do too much checking for null when using the 4.0 API; e.g. checking if tracer is null.
> In 3.x, there was an isTracing but now you have to get Span from Scope and if it is null, then you know you are not tracing... not as obvious as isTracing.
> TraceScope is meant as the Tracing Interface; it hides Spans. Its coverage is not complete though. For example, to add a Parent, you have to get the Span from the Scope and add the Parent there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)