forked from apache/spark
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SPARK-49632][SQL] Remove the ANSI config suggestion in CANNOT_PARSE_…
…TIMESTAMP ### What changes were proposed in this pull request? This PR changes the message returned on a failure of `ToTimestamp` family of expressions. ### Why are the changes needed? CANNOT_PARSE_TIMESTAMP contains suggested fix for turning off ANSI mode. Now that in Spark 4.0.0 we have moved to ANSI mode on by default, we want to keep suggestions of this kind to the minimum. ### Does this PR introduce _any_ user-facing change? Yes, error message is changing. ### How was this patch tested? Existing tests span the error message change. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#49227 from mihailom-db/cannot_parse_timestamp. Authored-by: Mihailo Milosevic <mihailo.milosevic@databricks.com> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
- Loading branch information
1 parent
2b1369b
commit 2cb66e6
Showing
9 changed files
with
3 additions
and
69 deletions.
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.