You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/27 11:31:04 UTC
[jira] [Commented] (CAMEL-11211) Remove deprecated SpanManager from
camel-opentracing
[ https://issues.apache.org/jira/browse/CAMEL-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986397#comment-15986397 ]
ASF GitHub Bot commented on CAMEL-11211:
----------------------------------------
GitHub user objectiser opened a pull request:
https://github.com/apache/camel/pull/1664
CAMEL-11211 Remove the deprecated SpanManager, which uses threadlocal…
…, and instead just manage the spans within the exchanges
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/objectiser/camel otctx
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1664.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1664
----
commit b12cbe7cf2865737ddbbe73f0eca3598f3d99ab7
Author: Gary Brown <ga...@brownuk.com>
Date: 2017-04-27T10:42:22Z
CAMEL-11211 Remove the deprecated SpanManager, which uses threadlocal, and instead just manage the spans within the exchanges
----
> Remove deprecated SpanManager from camel-opentracing
> ----------------------------------------------------
>
> Key: CAMEL-11211
> URL: https://issues.apache.org/jira/browse/CAMEL-11211
> Project: Camel
> Issue Type: Improvement
> Reporter: Gary Brown
>
> The current implementation uses the SpanManager from the opentracing-contrib org. Span management is currently being integrated more into the core opentracing-java APIs, and therefore would need to change in the near future.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)