CC-26777: Cherry pick fix for potential NullPointerException for Kafka headers with null value. #57
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
In Connect, a message Header can be null, so additional null-checks are required when processing header values e.g. for the Splunk index, to avoid an NPE. Adds a failing -> passing test.
aniketshrimal
approved these changes
Mar 28, 2025
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.
In Connect, a message Header can be null, so additional null-checks are required when processing header values e.g. for the Splunk index, to avoid an NPE.
Adds a failing -> passing test.
Cherry pick PR : splunk#414
JIRA : https://confluentinc.atlassian.net/browse/CC-26777
Problem
Solution
Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Release Plan