[
https://issues.apache.org/jira/browse/HTRACE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272715#comment-15272715
]
Hudson commented on HTRACE-359:
-------------------------------
SUCCESS: Integrated in HTrace-Master #253 (See
[https://builds.apache.org/job/HTrace-Master/253/])
HTRACE-359. TraceRunnable and TraceCallable should be built using parent
(cmccabe: rev 699ee9918f18f7f06fcff99f39952dc09e1ab8c7)
* htrace-core4/src/main/java/org/apache/htrace/core/TraceRunnable.java
* htrace-core4/src/main/java/org/apache/htrace/core/TraceCallable.java
* htrace-core4/src/main/java/org/apache/htrace/core/Tracer.java
* htrace-core4/src/test/java/org/apache/htrace/core/TestTraceExecutor.java
> TraceRunnable and TraceCallable should be built using 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
> Fix For: 4.2
>
> Attachments: HTRACE-359.patch.txt, HTRACE-359.patch.txt,
> HTRACE-359.v3.patch.txt, HTRACE-359.v4.patch.txt
>
>
> 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)
