-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-49428][SQL] Move Connect Scala Client from Connector to SQL #49695
base: master
Are you sure you want to change the base?
Conversation
spark/.github/workflows/maven_test.yml Line 197 in aa24a9a
We need to correct some parts of the maven_test.yml file, and at the same time, consider how to ensure compatibility if there are differences in code structure between the master and branch-4.0 now, as this yml file will also be used for the Maven daily test in branch-4.0. |
Line 195 in 04f862a
Line 209 in 04f862a
The configuration in the
|
@LuciferYang yeah I was afraid of that. Thanks for the heads-up! |
@LuciferYang do you think this is good to go? I will port this to 4.0 as well. |
Let me double-check that |
There may still be some code that needs to be fixed: spark/sql/connect/server/README.md Line 4 in 6bbfa2d
spark/sql/connect/common/README.md Line 4 in 6bbfa2d
spark/docs/spark-connect-overview.md Line 250 in 6bbfa2d
spark/docs/_plugins/build_api_docs.rb Lines 149 to 156 in 6bbfa2d
Lines 37 to 44 in 6bbfa2d
Lines 222 to 227 in 6bbfa2d
spark/dev/protobuf-breaking-changes-check.sh Lines 36 to 39 in 6bbfa2d
spark/dev/sparktestsupport/modules.py Lines 332 to 343 in 6bbfa2d
@hvanhovell Could you please review the above file again? Of course, I don't object to fixing some of them in separate pull requests. |
It looks like you've fixed them in the latest commit :), let's wait for the latest CI results. |
@@ -35,7 +35,7 @@ fi | |||
|
|||
pushd sql/connect/common/src/main && | |||
echo "Start protobuf breaking changes checking against $BRANCH" && | |||
buf breaking --against "https://github.com/apache/spark.git#branch=$BRANCH,subdir=connector/connect/common/src/main" && | |||
buf breaking --against "https://github.com/apache/spark.git#branch=$BRANCH,subdir=sql/connect/common/src/main" && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we perform a branch version check here? If BRANCH
is branch-3.x, should we keep comparing it with connector/connect/common/src/main
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we run that against 3.5/3.4?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
branch-4.0 will against branch-3.5, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where do we run that? I grepped through to the code base and I can't find us using it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was used in build_and_test.yml
, but no more.
@HyukjinKwon is this a dead file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shouldn't be used in GitHub Actions, because GitHub Actions uses the following configuration:
spark/.github/workflows/build_and_test.yml
Lines 752 to 756 in 6bbfa2d
- name: Breaking change detection against branch-4.0 | |
uses: bufbuild/buf-breaking-action@v1 | |
with: | |
input: sql/connect/common/src/main | |
against: 'https://github.com/apache/spark.git#branch=branch-4.0,subdir=sql/connect/common/src/main' |
Judging from the commit history, this seems more like a tool for local use by developers? It would be best to have @grundprinzip, @HyukjinKwon , or @zhengruifeng , who have modified this file, confirm it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @hvanhovell
I have locally checked the Maven compilation and tested the three modules related to Connect, including connect-common, connect, and connect-client-jvm, and they are all ok.
What changes were proposed in this pull request?
This PR moves the connect Scala JVM client project to sql. It also moves the connect/bin and connect/doc to sql.
Why are the changes needed?
Connect is part of the sql project now. It is weird to keep these seperate.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.
Was this patch authored or co-authored using generative AI tooling?
No.