Improve access path validation#7575
Closed
aajisaka wants to merge 1 commit into
Closed
Conversation
aajisaka
added a commit
that referenced
this pull request
Jul 17, 2026
### Why are the changes needed? Normalize config keys before access path validation ### How was this patch tested? Added unit tests ### Was this patch authored or co-authored using generative AI tooling? Assisted by: GPT-5.5 Closes #7575 from aajisaka/fix-spark-access-path. Closes #7575 9c1b472 [Akira Ajisaka] Improve access path validation Authored-by: Akira Ajisaka <aajisaka@apache.org> Signed-off-by: Akira Ajisaka <aajisaka@apache.org> (cherry picked from commit 7066271) Signed-off-by: Akira Ajisaka <aajisaka@apache.org>
Member
Author
|
Thank you! Merged into master and branch-1.12. |
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
2 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.
Why are the changes needed?
Normalize config keys before access path validation
How was this patch tested?
Added unit tests
Was this patch authored or co-authored using generative AI tooling?
Assisted by: GPT-5.5