[SPARK-34451][SQL] Add alternatives for datetime rebasing SQL configs and deprecate legacy configs #31576
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?
Move the datetime rebase SQL configs from the
legacynamespace by:spark.sql.legacy.parquet.datetimeRebaseModeInRead->spark.sql.parquet.datetimeRebaseModeInRead.Why are the changes needed?
The rebasing SQL configs like
spark.sql.legacy.parquet.datetimeRebaseModeInReadcan be used not only for migration from previous Spark versions but also to read/write datatime columns saved by other systems/frameworks/libs. So, the configs shouldn't be considered as legacy configs.Does this PR introduce any user-facing change?
Should not. Users will see a warning if they still use one of the legacy configs.
How was this patch tested?