[Prototype] How to support complex attributes in logs/events? (Option D) #6973
Conversation
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
trask
changed the title
jack-berg
reviewed
Dec 19, 2024
| */ | ||
| // TODO (trask) how to use pre-encoded key? | ||
| // - is ComplexAttributeKey too broad (covers all nested attribute types)? | ||
| default LogRecordBuilder setAttribute(String key, ComplexAttribute value) { |
Member
There was a problem hiding this comment.
Why introduce a new ComplexAttribute type instead of just setAttribute(String, Value)?
Only reason I can think of is for code generation in semantic-convention-java.
Member
Author
|
Closing in favor of #6983 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Exploring @jack-berg's #6960 (comment)