[#2451] feat(spark-connector): support Float and Double type for spark-connector #2484
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
|
LGTM, but CI is not triggered because #2485, please wait it merged |
FANNG1
added a commit
that referenced
this pull request
Mar 11, 2024
…#2485) ### What changes were proposed in this pull request? add spark-connector to auto trigger CI ### Why are the changes needed? if only change spark connector code, CI are not triggered, like #2484 ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? existing UT
FANNG1
approved these changes
Mar 11, 2024
|
@ichuniq , merged to main, thanks for your work! |
This was referenced Mar 19, 2024
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?
Support Float and Double type for spark-connector; add related test
Why are the changes needed?
Fix: #2451
Does this PR introduce any user-facing change?
No
How was this patch tested?
./gradlew test -PskipITs