Minimal attempt to support Spark 3.3 by adding shims for CSVOptions methods #524
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
…ethods Signed-off-by: Sean Owen <srowen@gmail.com>
|
Pushing this through and will fix tests later. Spark 3.X support |
rlgarris
approved these changes
Jan 24, 2023
rlgarris
approved these changes
Jan 24, 2023
|
Pushing through these changes. |
|
Done. |
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 are proposed in this pull request?
This change minimally enables compiling and running on Spark 3.3, by shimming over one new difference - date/time format fields in CSVOptions changed.
How is this patch tested?
Note that there appear to be existing test failures (?)
I also don't know if this actually works on Spark 3.1/2.4, but, those seem unsupported?