You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2016/04/19 17:42:25 UTC
[jira] [Commented] (HTRACE-359) TraceRunnable and TraceCallable
should store parent spanId not scope
[ https://issues.apache.org/jira/browse/HTRACE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248003#comment-15248003 ]
Mike Drob commented on HTRACE-359:
----------------------------------
Also, TraceCallable should have a public constructor to match TraceRunnable.
> TraceRunnable and TraceCallable should store parent spanId not scope
> --------------------------------------------------------------------
>
> Key: HTRACE-359
> URL: https://issues.apache.org/jira/browse/HTRACE-359
> Project: HTrace
> Issue Type: Bug
> Components: core
> Affects Versions: 4.0
> Reporter: Mike Drob
> Assignee: Mike Drob
>
> TraceRunnable/Callable both take a parent TraceScope and extract the span Id from it when executing the task. Instead, we should allow users to create custom TraceRunnable/Callable instances with only a SpanId instead of a full TraceScope, for instance when reading a span id from an RPC call and a TraceScope object is not available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)