feat: use shared otlp types#2236
Open
thompson-tomo wants to merge 4 commits into
Open
Conversation
thompson-tomo
force-pushed
the
otlp_consolidation
branch
from
July 12, 2026 06:17
ca6206d to
14904de
Compare
thompson-tomo
marked this pull request as ready for review
July 12, 2026 14:53
thompson-tomo
requested review from
a team,
dazuma,
fbogsany,
kaylareopelle,
mwear,
robbkidd,
robertlaurin and
xuan-cao-swi
as code owners
July 12, 2026 14:53
thompson-tomo
force-pushed
the
otlp_consolidation
branch
6 times, most recently
from
July 15, 2026 02:44
cad2098 to
87cae52
Compare
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Progresses: #2170
This ensures all otlp exporters use the otlp-common package which has a dependency on the new types-otlp gem which is generated based on proto.
It was considered to put the types in common however that makes for difficult versioning. But more significantly by separating them, it provides an architecture which will enable us to address the current jruby limitation.
Follow up steps will be: