This repository has been archived by the owner on Apr 28, 2022. It is now read-only.
Added support for 128bit to B3 decoder #144
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
Fixes #143
Short description of the changes
Currently, B3 TraceId extraction only supports fallback to 64 bit. Since other tracers by now also support 128 bit, the behavior was aligned with the regular
TextMapCodecagain.The
HexCodecclass was removed since it's redundant now with theFromStringimplementations ofSpanIdandTraceId.B3TextMapCodecearlier returnednullon problems. Due to using theExceptionCatchingExtractorDecorator, it's better to throw an exception that gets logged and still gracefully returnsnull.