Re: [EXTERNAL] Re: Move Date and Timestamp parsing from ResolverStyle.LENIENT to ResolverStyle.STRICT

Hi all, Thanks for pushing this forward Ashish! Actually I am not in favor of creating a flag for this. Either we decide consciously to break backward compatibility in the hope that we are improving the expected results or we keep the current behavior. Adding another flag means that we maintain a

Re: [EXTERNAL] Re: Move Date and Timestamp parsing from ResolverStyle.LENIENT to ResolverStyle.STRICT

Hello, Is anyone able to try out a few different vendor RDBMS to see how they handle invalid dates, or provide links to documentation, both for invalid formatting and things like mm-dd-yyy 12-40-2021? Thanks. On Tue, Jul 13, 2021 at 5:14 AM Sankar Hariappan wrote: > I'm supporting this change

Flaky tests

Hi Team, Recently I have seen plenty of flaky tests again in the pre-commit runs but only seen Zoltan's commits to handle these tests. Some time ago Zoltan Haindrich created a nice tool to check for flaky tests for everyone: - http://ci.hive.apache.org/job/hive-flaky-check/

[jira] [Created] (HIVE-25327) CLONE - Mapjoins in HiveServer2 fail when jmxremote is used

louiechen created HIVE-25327: Summary: CLONE - Mapjoins in HiveServer2 fail when jmxremote is used Key: HIVE-25327 URL: https://issues.apache.org/jira/browse/HIVE-25327 Project: Hive Issue Type:

RE: [EXTERNAL] Re: Move Date and Timestamp parsing from ResolverStyle.LENIENT to ResolverStyle.STRICT

I'm supporting this change to return "NULL" for invalid date/timestamp. In the interest of backward compatibility, can we make all these changes under a flag which can be enabled by default? Thanks, Sankar -Original Message- From: David Sent: 10 July 2021 07:35 To: dev Cc: sank...@ap