Fix nz timestamp unit tests #8145
Merged
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
…er inferTimestampNTZ config Signed-off-by: Navin Kumar <[email protected]>
|
build |
revans2
approved these changes
Apr 19, 2023
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.
Fixes #7754.
Spark 3.4 actually removed the "heavier"
"spark.sql.parquet.timestampNTZ.enabledconfiguration option (which prevented both inference and writing timestampNTZ with Parquet), and added thespark.sql.parquet.inferTimestampNTZ.enabledconfiguration option which only controls inference of the timestampNTZ type on reading Parquet (See apache/spark#39856)This PR fixes the configuration so the unit test passes.