Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update Binary format in the Specification #437

Closed
carlosalberto opened this issue Feb 4, 2020 · 12 comments
Closed

Update Binary format in the Specification #437

carlosalberto opened this issue Feb 4, 2020 · 12 comments
Assignees
@carlosalberto
Labels
area:api Cross language API specification issue spec:context Related to the specification/context directory triage:deciding:tc-inbox Needs attention from the TC in order to move forward
Milestone
v0.6

Comments

@carlosalberto
Copy link
Contributor

carlosalberto commented Feb 4, 2020 •
edited
Loading

As #426 is temporarily removing Binary format, we need to make sure Binary is re-added and updated properly with the OTEP 66 updates.

Assigning for now to @MikeGoldsmith but we can discuss who can tackle this item going forward.
@carlosalberto carlosalberto added this to the Alpha v0.4 milestone Feb 4, 2020
@carlosalberto carlosalberto mentioned this issue Feb 4, 2020
Merged
@bogdandrutu
Copy link
Member

Added @carlosalberto to the assignees since he promised to add it back :)

@carlosalberto
Copy link
Contributor Author

That works :)

@Oberon00
Copy link
Member

Can we assign a milestone for this issue? Any release that wants to offer a full OpenTracing or OpenCensus compatibility layer will need this feature.

@Oberon00
Copy link
Member

Also, we need that feature at Dynatrace and will have to stay on an older version of the Java API until this is fixed.

@carlosalberto
Copy link
Contributor Author

@Oberon00 So the milestone would be 0.5.0 - for which we don't have a date for yet (other than being the next important milestone). Maybe we need to discuss this in the next SIG/community call, to plan what/how happens after beta ;)

@carlosalberto carlosalberto mentioned this issue Apr 27, 2020
Merged
@Oberon00 Oberon00 mentioned this issue Jun 7, 2020
Closed
@carlosalberto carlosalberto modified the milestones: v0.5, v0.6 Jun 9, 2020
@arminru arminru added the spec:context Related to the specification/context directory label Jun 9, 2020
@bogdandrutu bogdandrutu added the area:api Cross language API specification issue label Jun 26, 2020
@carlosalberto carlosalberto added the release:required-for-ga Must be resolved before GA release, or nice to have before GA label Jul 2, 2020
@reyang reyang added the priority:p2 Medium priority level label Jul 24, 2020
@andrewhsu
Copy link
Member

Talked with @carlosalberto today and based on the history of the intention of binary format (it looks like it was only desired to be temporarily removed), looks like this one is important to get in sooner because it can cause backward breaking change. Therefore, changing priority to p1.

@andrewhsu andrewhsu added priority:p1 Highest priority level and removed priority:p2 Medium priority level labels Aug 5, 2020
@andrewhsu
Copy link
Member

from the spec issue triage mtg today, discussed this and moving to after ga

@andrewhsu andrewhsu added release:after-ga Not required before GA release, and not going to work on before GA and removed priority:p1 Highest priority level release:required-for-ga Must be resolved before GA release, or nice to have before GA labels Sep 18, 2020
@dashpole dashpole mentioned this issue Oct 29, 2020
Closed
@Oberon00 Oberon00 mentioned this issue Nov 18, 2020
Merged
@calohmn calohmn mentioned this issue Apr 12, 2022
Merged
@dashpole dashpole mentioned this issue Dec 14, 2022
Merged
@shaun-cox shaun-cox mentioned this issue May 24, 2023
Closed
4 tasks
@annabokhan
Copy link

Documentation states that the binary propagator support is upcoming, however this thread has been stale for almost 4 years. Is this still planned?

@amalgawa
Copy link

+1 to above question. It has been 4 years, since no activity. If there are any prior investigations why it was no longer pursued, I can probably help implement it.

@svrnm
Copy link
Member

svrnm commented May 6, 2024

@carlosalberto what is the status of this one?

@svrnm svrnm added triage:deciding:needs-info Not enough information. Left open to provide the author with time to add more details and removed release:after-ga Not required before GA release, and not going to work on before GA labels May 6, 2024
@esemeniuc
Copy link

+1 need to see this

@trask trask added triage:deciding:tc-inbox Needs attention from the TC in order to move forward and removed triage:deciding:needs-info Not enough information. Left open to provide the author with time to add more details labels Jun 14, 2024
@jack-berg
Copy link
Member

Discussed in the 7/17/24 TC meeting. We're closing this for the time being for:

  • niche use case / low demand
  • lack of performance benchmarks indicating benefit
  • protocols really need binary support baked in
  • seems more appropriate to drive at W3C level, and that effort has delayed and stalled

If the W3C binary traceparent effort picks back up, we should re-open this issue and implement in OpenTelemetry.

@pellared pellared closed this as not planned Won't fix, can't repro, duplicate, stale Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carlosalberto carlosalberto

Labels
area:api Cross language API specification issue spec:context Related to the specification/context directory triage:deciding:tc-inbox Needs attention from the TC in order to move forward
Projects
None yet
Milestone
v0.6
Development

No branches or pull requests