Conversation
wForget
force-pushed
the
UNIFFLE-2792
branch
from
September 18, 2026 07:04
c9da111 to
1ccd563
Compare
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
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?
Add no-argument constructors and JavaBean setters to Uniffle listener events and their nested metric/timing objects so Spark History Server can deserialize them.
Make the relevant metric fields mutable while preserving existing constructors and JSON property names. Add serialization compatibility tests and align test-scoped Jackson dependencies with the selected Spark profile.
Why are the changes needed?
Opening an application's history page can fail with HTTP 500:
Older Jackson Scala modules inferred constructor parameter names for these Java classes. Newer versions restrict this behavior, leaving Uniffle events without a supported deserialization constructor.
closes #2792
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually verified that the previously failing application history page opens successfully on Spark 4.2.0 History Server after applying this patch.