[
https://issues.apache.org/jira/browse/HTRACE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246621#comment-15246621
]
Hudson commented on HTRACE-355:
-------------------------------
SUCCESS: Integrated in HTrace-Master #247 (See
[https://builds.apache.org/job/HTrace-Master/247/])
HTRACE-355. TraceRunnable and TraceCallable should pull description from
(cmccabe: rev 23e2dce78ebbc1d1501399ff681c2bf7ddc36b71)
* 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/test/java/org/apache/htrace/core/TestTraceExecutor.java
* htrace-core4/src/main/java/org/apache/htrace/core/Tracer.java
> TraceRunnable and TraceCallable should pull description from child thread
> instead of parent
> -------------------------------------------------------------------------------------------
>
> Key: HTRACE-355
> URL: https://issues.apache.org/jira/browse/HTRACE-355
> Project: HTrace
> Issue Type: Bug
> Components: core
> Affects Versions: 4.0
> Reporter: Mike Drob
> Assignee: Mike Drob
> Fix For: 4.2
>
> Attachments: HTRACE-355.patch.txt, HTRACE-355.patch.txt
>
>
> If a TraceRunnable or TraceCallable is passed a null scope name, then it will
> set the description to the current thread's name, which happens to be the
> parent thread. It would be much more useful to set the description to the
> child thread's name.
> A nice side effect of this change is that we can add a version of
> {{tracer.newTraceExecutor}} that doesn't need to take a description for use
> by applications that take great care to name their threads in an informative
> manner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
