Fix IllegalArgumentException: Unrecognized AnyValue type on empty LogRecord.body#2529
Merged
breedx-splk merged 3 commits intoopen-telemetry:mainfrom Jan 30, 2026
Merged
Conversation
breedx-splk
reviewed
Jan 9, 2026
Contributor
breedx-splk
left a comment
There was a problem hiding this comment.
@dshkil thanks for catching and addressing this edge case. Would it be possible to please add a test case that covers this? Appreciate it.
66cc014 to
370ed41
Compare
|
Unit tests have been updated |
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
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.
Description:
Bug fix - LogRecord with a body equal to an empty string cannot be mapped to an SDK's Value. It happens on periodic export in the background and causes an unhandled exception.
In this case,
AnyValuedeserialized using protobuf has all its fields set to null. It makes impossible to determine the original body value type. However, according toLogRecordDataMapper.bodyToAnyValue(), the only possible non-null values are strings.I suppose the root cause is related to the LogRecord protobuf schema. However, changes to the schema could be problematic, and we also need a workaround for existing data.
Existing Issue(s):
#2530
Testing:
Tested in the app
Documentation:
No functional changes
Outstanding items:
No functional changes