[SPARK-54565][CORE] SparkBuildInfo should load spark-version-info.properties from its own classloader
#53279
+2
−2
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?
Change SparkBuildInfo to use its own classloader instead of thread context classloader to load
spark-version-info.properties.Why are the changes needed?
I hit an issue during the Connect JDBC driver & JetBrains DataGrip integration.
After adding some debug messages, I found it was caused by using wrong classloader.
Similar issue that affects Hive JDBC driver and Spark's Isolated Classloader (see SPARK-32256) was fixed by HADOOP-14067
Does this PR introduce any user-facing change?
This fixes corner issues that the application uses multiple classloaders with Spark libs.
How was this patch tested?
Pass GHA to ensure the change breaks nothing, also manually verified the Connect JDBC driver & JetBrains DataGrip integration.
Was this patch authored or co-authored using generative AI tooling?
No.