Enhanced the close() method with defensive null checks to prevent NullPointerException during resource cleanup #17110
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.
File Modified:
FixedByteSingleValueMultiColumnReaderWriter.javaLocation:
pinot-segment-local/src/main/java/org/apache/pinot/segment/local/io/readerwriter/impl/FixedByteSingleValueMultiColumnReaderWriter.javaImprovement: Enhanced the
close()method with defensive null checks to prevent NullPointerException during resource cleanup.Before:
After:
Impact
✅ Prevents NullPointerException during resource cleanup
✅ Improves robustness of the close() method
✅ Follows defensive programming best practices
✅ No functional changes to normal operation
✅ Low risk - purely defensive improvement