[SPARK-51855] Support Spark SQL REPL
#77
Closed
Conversation
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
dongjoon-hyun
force-pushed
the
SPARK-51855
branch
from
7ce752d to
592845f
Compare
viirya
approved these changes
Apr 21, 2025
Package.swift
Outdated
| ] | ||
| ), | ||
| .executableTarget( | ||
| name: "SQLRepl", |
There was a problem hiding this comment.
Do we need to add Spark prefix? I.e., SparkSQLRepl?
There was a problem hiding this comment.
Thank you. Sure, let me add it. :)
|
Merged to main. |
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?
This PR aims to support
Spark SQL REPLviaSpark Connect for Swiftlibrary.Why are the changes needed?
This is helpful for the users in two ways.
Spark Connect for Swiftlibrary for the production, development and testing.Does this PR introduce any user-facing change?
No, this is a new
executabletarget of this project in addition to the existinglibrarytarget.How was this patch tested?
Manual review by following new
README.mdcontent.Was this patch authored or co-authored using generative AI tooling?
No.