[WIP][ISSUE-4346] Support Spark 3.5 #4354
Open
Conversation
This file contains 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
|
Thanks David, start this pull request. please also remove the old spark version integration code. |
jackylk
reviewed
Apr 14, 2024
format/pom.xml
Outdated
| @@ -37,7 +37,7 @@ | |||
| <dependency> | |||
| <groupId>org.apache.thrift</groupId> | |||
| <artifactId>libthrift</artifactId> | |||
| <version>0.9.3</version> | |||
| <version>0.19.0</version> | |||
There was a problem hiding this comment.
It is better we do this in another PR. I am preparing a PR for this.
QiangCai
force-pushed
the
integration_spark3.5
branch
from
739a5b1
to
cb96c8b
Compare
|
please solve some conflicts. |
QiangCai
force-pushed
the
integration_spark3.5
branch
from
e8c4ae8
to
122a544
Compare
|
@QiangCai I saw you submitted 5 commits to community in last week, please let us know the latest progress about this PR |
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.
Why is this PR needed?
What changes were proposed in this PR?
Does this PR introduce any user interface change?
Is any new testcase added?