[Bug] Fix Spark application list pagination restoration - #4514
Open
gordan-zhang wants to merge 2 commits into
Open
[Bug] Fix Spark application list pagination restoration#4514gordan-zhang wants to merge 2 commits into
gordan-zhang wants to merge 2 commits into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
|
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
Issue Number: close #4513
Align the session storage key read by the Spark application list with the Spark-specific key written by the edit action. This restores the previous page after returning from edit without sharing pagination state with the Flink application module.
Brief change log
sparkAppPageNowhen the Spark application list mounts.Verifying this change
git diff --checksuccessfully.sparkAppPageNo.Does this pull request potentially affect one of the following parts