Skip to content
This repository has been archived by the owner on May 23, 2023. It is now read-only.

V0.32.0 #337

Merged
merged 29 commits into from
Mar 25, 2019
Merged

V0.32.0 #337

merged 29 commits into from
Mar 25, 2019

Conversation

carlosalberto
Copy link
Collaborator

No description provided.

carlosalberto and others added 28 commits March 28, 2018 18:33
It's not a common scenario to use a Tag *key* as the tag value.
* Implement Trace Identifiers.
* Bump JaCoCo to use a Java 10 friendly version (#306)

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

* Set version in `v0.32.0` branch to `0.32.0-SNAPSHOT`

Fixes #308
* Deprecate finishSpanOnClose on activation.
* Add ScopeManager.activeSpan() and Tracer.activateSpan().
* Clarify the API changes and deprecations.
* Add a error reporting sample to opentracing-testbed.
* Implement a simple layer on top of ByteBuffer for BINARY format.
Reduces the need to call Tags.SOMETAG.getKey() and adds type safety for setTag if done from the span.

Fixes #271
* Allow injecting into maps of type Map<String,Object>

For the inject case, it doesn’t matter so much that the generic type is declared as String.

* Modify generic type on map in test.
This is done so we don't end up using an abstract class in the public API.
* Add simple registerIfAbsent to global tracer
It seems the previous one expired or was discarded.
If we had separate formats for inject and extract this refactor would have been much cleaner.

This allows us to better avoid partially implementing the TextMap interface and throwing an exception for the other method.

Since Binary is a new addition, I applied a similar refactoring to that.

Closes #315.
* Deprecate ScopeManager.active() and update related code.
* Rename common_request_handler to concurrent_common_request_handler.
* Add a testbed case for request handlers having no storage for Scope.
* Make Tracer extends Closable.
* Update the README with the latest changes.
This one does not really need to be synchronized.
The field itself is volatile and that is enough.
* Add a deprecation note for AutoFinishScopeManager/AutoFinishScope.
* Add a clarification on why we are deprecating this.
* Mention the Issue that lead to deprecating auto finish.
@carlosalberto
Copy link
Collaborator Author

Hey - created a PR prior to releasing 0.32.0 (including updating the CHANGELOG).

Let me know ;)

@felixbarny
Copy link
Contributor

Is this release fully backwards compatible?

@tylerbenson
Copy link

@felixbarny It should be compatible for users, but implementations will require some changes.

@carlosalberto
Copy link
Collaborator Author

Hey @felixbarny yes, it's as @tylerbenson said

As an exception: for users, they will be impacted if they use inject/extract with adapters themselves, i.e.

tracer.inject(context, Format.Builtin.TEXT_MAP, new TextMapInjectAdapter(map));

to:

tracer.inject(context, Format.Builtin.TEXT_MAP_INJECT, new TextMapInjectAdapter(map)); // Or...
tracer.inject(context, Format.Builtin.TEXT_MAP, new TextMapAdapter(map));

Copy link
Contributor

@sjoerdtalsma sjoerdtalsma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately I don't have time to go over all changes in a single go, but assuming all these are PR's that were individually reviewed already, I approve

CHANGELOG.md Outdated
* Split Inject and Extract builtin interfaces.
* `Tracer` implements `Closable`.
* Added `GlobalTracer.registerIfAbsent()`.
* Added `GlobalTracer.isRegistered()`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GlobalTracer.isRegistered() already existed. The implementation changed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, right. Thanks for the review. Will update the Changelog ;)

@@ -20,7 +20,7 @@
<parent>
<groupId>io.opentracing</groupId>
<artifactId>parent</artifactId>
<version>0.31.1-SNAPSHOT</version>
<version>0.32.0-RC3-SNAPSHOT</version>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we do an RC3?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we are ready for an actual release - the latest (important) change from RC2 is making Tracer implement Closable ;)

@carlosalberto carlosalberto merged commit ed1925b into master Mar 25, 2019
@codefromthecrypt
Copy link
Contributor

Hey @felixbarny yes, it's as @tylerbenson said

As an exception: for users, they will be impacted if they use inject/extract with adapters themselves, i.e.

tracer.inject(context, Format.Builtin.TEXT_MAP, new TextMapInjectAdapter(map));

to:

tracer.inject(context, Format.Builtin.TEXT_MAP_INJECT, new TextMapInjectAdapter(map)); // Or...
tracer.inject(context, Format.Builtin.TEXT_MAP, new TextMapAdapter(map));

this should be added to the change log. can you do that? Also, It could be that TEXT_MAP_EXTRACT is also new? It is harder to tell without @since tags on the apis.

@tylerbenson
Copy link

@adriancole yes, both TEXT_MAP_INJECT and TEXT_MAP_EXTRACT were added in this release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants