Add null check in DelegatingBlockReader#toString() and unit tests #18677
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 are proposed in this PR?
This PR adds a null check in the
DelegatingBlockReader#toString()
method to handle cases where the underlyingBlockReader
is null. This prevents potential NullPointerException during thetoString()
call.Additionally, unit tests were added to verify this new behavior.
Why are the changes needed?
The change ensures that the
DelegatingBlockReader
can gracefully handle cases where the underlyingBlockReader
is null, which improves robustness.Does this PR introduce any user-facing changes?
No.
How was this patch tested?
Unit tests have been added and verified with the current testing framework.