[SPARK-50082][CORE] Remove some unnecessary Jersey-related warning logs #48611
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?
This PR aims to remove some unnecessary Jersey-related warning logs when
ApiRootResource
orPrometheusResource
api was called.To reproduce, when we start spark-shell with the latest master code, open the Spark UI, click the executor tab, you can see relevant warning logs appearing in the spark-shell.
There are some related pr and issues about jersey:
And we can solve these warning logs by setting some properties.
Why are the changes needed?
Remove unnecessary warning logs.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual check. After this pr, the warning logs are removed.
Was this patch authored or co-authored using generative AI tooling?
No.