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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inline incubating attributes + central semconv-incubating dependency #1298
Inline incubating attributes + central semconv-incubating dependency #1298
Changes from 3 commits
58e0e32
e26e173
87a8e4b
6723814
30b3f81
a78fea3
f07378d
a3b01cf
a24fd04
491f349
69872b3
1886937
67fc874
2ec01c6
4da5808
891de38
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All these usages of
opentelemetry-semconv-incubating
go against our stated advice:I think we should follow our own advice to avoid unresolvable transitive version conflicts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the reminder, I completely missed it.
I'm definitely missing the context on the intent of this advice, so maybe there is something to clarify here.
For now, the way I understand things:
The
opentelemetry-semconv
artifact only contains stable semantic conventions.The
opentelemetry-semconv-incubating
artifact only contains incubating semantic conventions.Consumers of semantic conventions who need/want to avoid breaking change:
opentelemetry-semconv
.opentelemetry-semconv-incubating
.Consumers of semantic conventions who can tolerate/handle breaking changes:
opentelemetry-semconv
opentelemetry-semconv-incubating
which provides an easy way to find usages and refactor in the IDE.For example:
To me, by adding a dependency on
opentelemetry-semconv-incubating
on a module in contrib, you opt-in for some breaking changes.Maybe here having a single version used for all the contrib modules is a bold move and having each module handle its own version (even if they are currently aligned) is a better compromise, so each module can be updated at its own pace.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After a bit of research I found that it comes from open-telemetry/semantic-conventions-java#41, and open-telemetry/semantic-conventions-java#22 (comment) provides some background on the issue with transitive dependencies.
However, this is something that we need to solve in a separate issue/PR, and maybe implementing a "per version namespace for the non-stable attributes" as suggested here in https://github.com/open-telemetry/semantic-conventions-java/ could help.
From what I understand the proposal is to have the generated semconv classes with a dedicated package per version (for example
io.opentelemetry.semconv.v1_25_0
) and to only keep a few older versions in the incubating artifact to prevent breaking existing usages.