[
https://issues.apache.org/jira/browse/HTRACE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972405#comment-14972405
]
Masatake Iwasaki commented on HTRACE-275:
-----------------------------------------
bq. ... I didn't want to make NullTracer a public class (reduce API surface).
NullTracer could be private nested subclass of Tracer to limit visibility
further.
bq. ... it feels kind of like a "fudge" to handle code that doesn't initialize
itself properly.
It is exactly for non-ideal world and we can say that it should not be used as
far as possible in documentation. Adding tracing to software having long
history may need this sometimes.
> Add NullTracer which never creates a trace span
> -----------------------------------------------
>
> Key: HTRACE-275
> URL: https://issues.apache.org/jira/browse/HTRACE-275
> Project: HTrace
> Issue Type: Improvement
> Components: api
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-275.001.patch
>
>
> [~iwasakims] suggested adding a {{NullTracer}} which never creates a trace
> span. This would be more convenient than checking tracer objects against
> null in some cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
