[#8304] fix: Possible NPE in LineageService#8997
Merged
justinmclean merged 1 commit intoapache:mainfrom Nov 2, 2025
Merged
Conversation
justinmclean
approved these changes
Nov 2, 2025
Member
justinmclean
left a comment
justinmclean
left a comment
There was a problem hiding this comment.
thanks for adding teh check
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
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.
What changes were proposed in this pull request?
Add a null check for the argument in dispatchLineageEvent and return false if it is null.
Why are the changes needed?
The method dispatchLineageEvent can throw a NullPointerException if called without proper initialization or with a null argument.
Fix: (#8304 )
Does this PR introduce any user-facing change?
no
How was this patch tested?
unit testing