[MINOR] Expose Gluten and component build information to SparkConf#11838
Merged
philo-he merged 1 commit intoapache:mainfrom Apr 7, 2026
Merged
[MINOR] Expose Gluten and component build information to SparkConf#11838philo-he merged 1 commit intoapache:mainfrom
philo-he merged 1 commit intoapache:mainfrom
Conversation
|
Run Gluten Clickhouse CI on x86 |
philo-he
changed the title
malinjawi
pushed a commit
to malinjawi/incubator-gluten
that referenced
this pull request
Apr 9, 2026
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
3 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 are proposed in this pull request?
Currently, Gluten build information is not injected into the Spark configuration, which causes difficulties in certain troubleshooting and tracking scenarios. For example:
Therefore, this PR sets the Gluten build information as part of the Spark configurations. With this change, we can simply check the build revision by looking at the Spark UI: