[HIVE-25306] Change Date/Timestamp parser from LENIENT to STRICT

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Component/s: Query Planning, UDF
• Labels: backwards-compatibility datetime pull-request-available timestamp
• Release Note: Breaking change
• Assignee: Ashish Sharma
• Reporter: Ashish Sharma
• Created: 05/Jul/21 12:35
• Updated: 02/Aug/23 13:08
• Resolved: 23/Jul/21 12:37

Description

Description -

Currently Date.java and Timestamp.java use DateTimeFormatter for parsing to convert the date/timpstamp from int,string,char etc to Date or Timestamp.

Default DateTimeFormatter which use ResolverStyle.LENIENT which mean date like "1992-13-12" is converted to "2000-01-12",

Moving DateTimeFormatter which use ResolverStyle.STRICT which mean date like "1992-13-12" is not be converted instead NULL is return.

https://docs.google.com/document/d/1YTTPlNq3qyzlKfYVkSl3EFhVQ6-wa9WFRdkdIeCoc1Y/edit?usp=sharing

Issue Links

• is related to: HIVE-4594 UDF should use setLenient(false) when using SimpleDateFormat for parsing given datestring
• is related to: HIVE-25056 cast ('000-00-00 00:00:00' as timestamp/datetime) results in wrong conversion
• is related to: HIVE-25576 Configurable datetime formatter for unix_timestamp, from_unixtime
• relates to: HIVE-17038 invalid result when CAST-ing to DATE
• relates to: HIVE-23129 Cast invalid string to date returns incorrect result
• relates to: HIVE-23752 Cast as Date for invalid date produce the valid output
• relates to: HIVE-2557 Inserting illegal timestamp behaves differently that in MySql
• links to: GitHub Pull Request #2445