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.

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

API: Consider specifying the maximum value of EntryTTL. #93

Closed
songy23 opened this issue Jun 10, 2019 · 2 comments
Closed

API: Consider specifying the maximum value of EntryTTL. #93

songy23 opened this issue Jun 10, 2019 · 2 comments
Labels
area:api Cross language API specification issue spec:context Related to the specification/context directory
Milestone

Comments

@songy23
Copy link
Member

songy23 commented Jun 10, 2019

From discussion: #73 (comment).

@songy23 songy23 added the area:api Cross language API specification issue label Jun 10, 2019
@songy23 songy23 added this to the API revision: 07-2019 milestone Jun 13, 2019
@iredelmeier iredelmeier added the spec:context Related to the specification/context directory label Jul 30, 2019
@SergeyKanzhelev SergeyKanzhelev removed this from the API revision: 07-2019 milestone Sep 27, 2019
@bogdandrutu bogdandrutu added this to the Alpha v0.3 milestone Sep 30, 2019
@jmacd
Copy link
Contributor

jmacd commented Jan 22, 2020

This must be addressed as we add OTEP 66 to the specification.

@jmacd
Copy link
Contributor

jmacd commented Jan 29, 2020

We believe this is no longer needed, as the spec for context propagation has eliminated Entry. See #420.

@jmacd jmacd closed this as completed Jan 29, 2020
TuckTuckFloof pushed a commit to TuckTuckFloof/opentelemetry-specification that referenced this issue Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:api Cross language API specification issue spec:context Related to the specification/context directory
Projects
None yet
Development

No branches or pull requests

5 participants