fix(parquet): support read i96 timestamp from parquet file

[sundy-li]

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/

Summary

Summary about this PR

It's compatible change:

create table t( a timestamp(0), b timestamp(3), d timestamp(6));
insert into t select now(), now(), now() from numbers(10);

create table t2( a timestamp(0), b timestamp(3), d timestamp(6));
insert into t2 select now(), now(), now() from numbers(10);

databend-query with Old/New version can read table t and t2.

Fixes #6627

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
databend	⬜️ Ignored (Inspect)		Jul 19, 2022 at 8:17AM (UTC)

[dantengsky]

• confirm that data(with timestamp column) generated by the old version, could be read by this PR

test_stateless_standalone_linux failed.

test_stateless_standalone_linux

03_0023_insert_into_array: [ FAIL ] - result differs with:
--- /workspace/tests/suites/0_stateless/03_dml/03_0023_insert_into_array.result 2022-07-18 04:15:39.394586214 +0000
+++ /workspace/tests/suites/0_stateless/03_dml/03_0023_insert_into_array.stdout 2022-07-18 04:19:11.488000857 +0000
@@ -1,3 +1,5 @@
+ERROR 1105 (HY000) at line 118: Code: 1104, displayText = called Result::unwrap() on an Err value: OutOfSpec("ListArray's child's DataType must match. However, the expected DataType is Timestamp(Microsecond, None) while it got Int64.").
+ERROR 1105 (HY000) at line 119: Code: 1054, displayText = Expected server error code: 1010 but got: 1002.
==Array(UInt8)==
1 [1, 2, 3]
2 [254, 255]
@@ -63,10 +65,6 @@
2021-01-01 2022-01-01
1990-12-01 2030-01-12
==Array(Timestamp)==
-1 ['2021-01-01 01:01:01.000000', '2022-01-01 01:01:01.000000']
-2 ['1990-12-01 10:11:12.000000', '2030-01-12 22:00:00.000000']
-2021-01-01 01:01:01.000000 2022-01-01 01:01:01.000000
-1990-12-01 10:11:12.000000 2030-01-12 22:00:00.000000
==Array(String)==
1 ['aa', 'bb']
2 ['cc', 'dd']

03_0023_insert_into_array_v2: [ FAIL ] - result differs with:
--- /workspace/tests/suites/0_stateless/03_dml/03_0023_insert_into_array_v2.result 2022-07-18 04:15:39.394586214 +0000
+++ /workspace/tests/suites/0_stateless/03_dml/03_0023_insert_into_array_v2.stdout 2022-07-18 04:19:15.588107257 +0000
@@ -1,3 +1,5 @@
+ERROR 1105 (HY000) at line 118: Code: 1104, displayText = called Result::unwrap() on an Err value: OutOfSpec("ListArray's child's DataType must match. However, the expected DataType is Timestamp(Microsecond, None) while it got Int64.").
+ERROR 1105 (HY000) at line 119: Code: 1054, displayText = Expected server error code: 1010 but got: 1002.
==Array(UInt8)==
1 [1, 2, 3]
2 [254, 255]
@@ -63,10 +65,6 @@
2021-01-01 2022-01-01
1990-12-01 2030-01-12
==Array(Timestamp)==
-1 ['2021-01-01 01:01:01.000000', '2022-01-01 01:01:01.000000']
-2 ['1990-12-01 10:11:12.000000', '2030-01-12 22:00:00.000000']
-2021-01-01 01:01:01.000000 2022-01-01 01:01:01.000000
-1990-12-01 10:11:12.000000 2030-01-12 22:00:00.000000
==Array(String)==
1 ['aa', 'bb']
2 ['cc', 'dd']

[BohuTANG]

• confirm that data(with timestamp column) generated by the old version, could be read by this PR

I think this issue needs to be a high priority #6557
Now it's a difficult for us to find the query layer compatibility issue, like this PR we need a strong test for it.

[dantengsky]

I think this issue needs to be a high priority #6557 Now it's a difficult for us to find the query layer compatibility issue, like this PR we need a strong test for it.

Agree. #6557 will be addressed just after #6639 closed

[dantengsky]

LGTM

[dantengsky]

LGTM

[b41sh]

LGTM