HIVE-24875: Unify InetAddress.getLocalHost() - #6784
Open
sayalimohite55 wants to merge 1 commit into
Open
sayalimohite55 wants to merge 1 commit into
sayalimohite55 wants to merge 1 commit into
Conversation
sayalimohite55
force-pushed
the
HIVE-24875
branch
from
September 15, 2026 13:21
4c8355c to
5a376c1
Compare
asf-ci-hive
added
tests pending
tests failed
and removed
tests failed
tests pending
labels
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?
Unified usage of getLocalHost, getCanonicalAddress methods from InetAddress removing repeatative exception handling logic and placing it in common utils classes for reuse.
Why are the changes needed?
InetAddress.getLocalHost() is accessed in different classes. It throws UnknownHostException which is handled differently everywhere. Unification of these calls is required for reusability and ensuring common graceful behavior across all calls.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Build