ft.com.invalid; sank...@apache.org;
> u...@hive.apache.org; David
> *Subject:* Re: [EXTERNAL] Re: Move Date and Timestamp parsing from
> ResolverStyle.LENIENT to ResolverStyle.STRICT
>
>
>
> Hi all,
>
>
>
> I also feel that adding more config doesn't make sense in t
To: dev@hive.apache.org
Cc: sankar.hariap...@microsoft.com.invalid; sank...@apache.org;
u...@hive.apache.org; David
Subject: Re: [EXTERNAL] Re: Move Date and Timestamp parsing from
ResolverStyle.LENIENT to ResolverStyle.STRICT
Hi all,
I also feel that adding more config doesn't make sen
> wrote:
> >
> >> 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?
> >>
>
p.
>> 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
>&
021 07:35
> To: dev
> Cc: sank...@apache.org; Stamatis Zampetakis
> Subject: [EXTERNAL] Re: Move Date and Timestamp parsing from
> ResolverStyle.LENIENT to ResolverStyle.STRICT
>
> Hello,
>
> I too would be in favor of this. It drastically cuts down on the test
> matrix fo
: dev
Cc: sank...@apache.org; Stamatis Zampetakis
Subject: [EXTERNAL] Re: Move Date and Timestamp parsing from
ResolverStyle.LENIENT to ResolverStyle.STRICT
Hello,
I too would be in favor of this. It drastically cuts down on the test matrix
for Hive if we can clamp down on timestamp formats. With
