-
Notifications
You must be signed in to change notification settings - Fork 897
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
Specify result of Resource.merge error #1726
Merged
carlosalberto
merged 1 commit into
open-telemetry:main
from
open-o11y:specify-result-of-resource-merge-error
Jun 7, 2021
Merged
Specify result of Resource.merge error #1726
carlosalberto
merged 1 commit into
open-telemetry:main
from
open-o11y:specify-result-of-resource-merge-error
Jun 7, 2021
Conversation
This file contains 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
tigrannajaryan
approved these changes
May 27, 2021
arminru
approved these changes
May 28, 2021
arminru
added
area:sdk
Related to the SDK
spec:resource
Related to the specification/resource directory
labels
May 28, 2021
MrAlias
approved these changes
Jun 1, 2021
cc @bogdandrutu |
6 tasks
bogdandrutu
approved these changes
Jun 7, 2021
carlosalberto
approved these changes
Jun 7, 2021
@dgetu Could you rebase this PR (or allow mantainers to update your branch)? |
The specification currently states that merging Resources and aggregating ResourceDetectors results in an error, but does not say anything about the resource with which the program continues to operate. This change specifies that the resultant resource of these methods is undefined and the decision is left to each implementation.
dgetu
force-pushed
the
specify-result-of-resource-merge-error
branch
from
June 7, 2021 17:54
072b426
to
045cfdf
Compare
Rebase done! |
I believe this is safe to include in 1.4.0. @carlosalberto unless anyone objects let's merge before 1.4.0 release. |
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
The specification currently states that merging Resources and aggregating ResourceDetectors results in an error, but does not say anything about the resource with which the program continues to operate. This change specifies that the resultant resource of these methods is undefined and the decision is left to each implementation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
The specification currently states that merging Resources and aggregating
ResourceDetectors results in an error, but does not say anything about the
resource with which the program continues to operate. This change specifies
that the resultant resource of these methods is undefined and the decision is
left to each implementation.