[SPARK-56695][SQL][DML] Remove Path Based Table support in SQL#56316
Closed
andreaschat-db wants to merge 1 commit into
Closed
[SPARK-56695][SQL][DML] Remove Path Based Table support in SQL#56316andreaschat-db wants to merge 1 commit into
andreaschat-db wants to merge 1 commit into
Conversation
aokolnychyi
pushed a commit
that referenced
this pull request
Jun 4, 2026
### What changes were proposed in this pull request? Current implementation for path based tables in SQL is partial. We are removing it for Spark 4.2. ### Why are the changes needed? The previous [attempt](#56039) to add path-based table support was halted due to concerns. For Spark 4.2 we are letting the connector handle it. ### Does this PR introduce _any_ user-facing change? No. Path based support in SQL was not yet released. ### How was this patch tested? Existing tests. ### Was this patch authored or co-authored using generative AI tooling? Claude Opus 4.7. Closes #56316 from andreaschat-db/dsv2TransactionRemoveSQLPathBasedSupport. Authored-by: Andreas Chatzistergiou <andreas.chatzistergiou@databricks.com> Signed-off-by: Anton Okolnychyi <aokolnychyi@apache.org> (cherry picked from commit 42db152) Signed-off-by: Anton Okolnychyi <aokolnychyi@apache.org>
aokolnychyi
pushed a commit
that referenced
this pull request
Jun 4, 2026
### What changes were proposed in this pull request? Current implementation for path based tables in SQL is partial. We are removing it for Spark 4.2. ### Why are the changes needed? The previous [attempt](#56039) to add path-based table support was halted due to concerns. For Spark 4.2 we are letting the connector handle it. ### Does this PR introduce _any_ user-facing change? No. Path based support in SQL was not yet released. ### How was this patch tested? Existing tests. ### Was this patch authored or co-authored using generative AI tooling? Claude Opus 4.7. Closes #56316 from andreaschat-db/dsv2TransactionRemoveSQLPathBasedSupport. Authored-by: Andreas Chatzistergiou <andreas.chatzistergiou@databricks.com> Signed-off-by: Anton Okolnychyi <aokolnychyi@apache.org> (cherry picked from commit 42db152) Signed-off-by: Anton Okolnychyi <aokolnychyi@apache.org>
Contributor
|
Thanks, merged into master/branch-4.x/branch-4.2. cc @huaxingao |
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.
What changes were proposed in this pull request?
Current implementation for path based tables in SQL is partial. We are removing it for Spark 4.2.
Why are the changes needed?
The previous attempt to add path-based table support was halted due to concerns. For Spark 4.2 we are letting the connector handle it.
Does this PR introduce any user-facing change?
No. Path based support in SQL was not yet released.
How was this patch tested?
Existing tests.
Was this patch authored or co-authored using generative AI tooling?
Claude Opus 4.7.