feat: integration test

[killme2008]

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

Main changes:

• Move more cases from duckdb to our integration tests, there are still many works to do.
• Fixed some issues when moving tests:
  • Supports if not exists when creating a database, and supports create schema in the parser too.
  • Column's time index option doesn't support bigint type and it can't be present in the last column.
  • Supports unsigned integer types, but not implemented in parser yet.
• There are also some issues not fixed yet
  • Not expected to run ExecutionPlan more than once #790
  • Physical planner does not support subquery expression #791
  • Catalog manager register_schema should supports create_if_not_exists #789
  • Supports prepare and execute statement #769
  • Supports INSERT INTO SELECT statement #760
  • Supports default value when inserting data. #759
  • select sum(float64) returns wrong result. #829

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

[killme2008]

After merging the Arrow flight service, looks like all tests fail:

Failed to execute, error: TonicStatus { addr: "127.0.0.1:4001", source: Status { code: Internal, message: "Failed to execute query: SelectExpr { expr: Some(Sql(\" DROP TABLE test;\")) }, source: Failed to do Flight get, source: status: Internal, message: \"Invalid SQL, error: expect SQL to be selection, actual:  DROP TABLE test;\", details: [], metadata: MetadataMap { headers: {} }", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Tue, 27 Dec 2022 06:52:27 GMT", "content-length": "0"} }, source: None }, backtrace: Backtrace(   0: backtrace::backtrace::libunwind::trace
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/backtrace-0.3.67/src/backtrace/libunwind.rs:93:5
<       backtrace::backtrace::trace_unsynchronized
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/backtrace-0.3.67/src/backtrace/mod.rs:66:5
<    1: backtrace::backtrace::trace
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/backtrace-0.3.67/src/backtrace/mod.rs:53:14
<    2: backtrace::capture::Backtrace::create
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/backtrace-0.3.67/src/capture.rs:176:9
<    3: backtrace::capture::Backtrace::new
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/backtrace-0.3.67/src/capture.rs:140:22
<    4: <snafu::backtrace_shim::Backtrace as snafu::GenerateImplicitData>::generate
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/snafu-0.7.4/src/backtrace_shim.rs:15:19
<       snafu::GenerateImplicitData::generate_with_source
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/snafu-0.7.4/src/lib.rs:1152:9
<    5: <client::error::TonicStatusSnafu<__T0> as snafu::IntoError<client::error::Error>>::into_error
<              at src/client/src/error.rs:20:17
<    6: <core::result::Result<T,E> as snafu::ResultExt<T,E>>::context
<              at /Users/dennis/.cargo/registry/src/github.1485827954.workers.dev-1ecc6299db9ec823/snafu-0.7.4/src/lib.rs:697:31
<    7: client::client::Client::batch::{{closure}}
<              at src/client/src/client.rs:143:22
<    8: client::client::Client::database::{{closure}}
<              at src/client/src/client.rs:127:38
<    9: client::database::Database::objects::{{closure}}
<              at src/client/src/database.rs:126:44

[codecov]

Codecov Report

Merging #770 (14615b2) into develop (32d5194) will decrease coverage by 0.16%.
The diff coverage is 82.35%.

@@             Coverage Diff             @@
##           develop     #770      +/-   ##
===========================================
- Coverage    86.10%   85.93%   -0.17%     
===========================================
  Files          421      421              
  Lines        55460    55549      +89     
===========================================
- Hits         47752    47735      -17     
- Misses        7708     7814     +106     

Flag	Coverage Δ
rust	85.93% <82.35%> (-0.17%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/datanode/src/error.rs	67.39% <ø> (ø)
src/datanode/src/instance.rs	50.00% <0.00%> (-20.26%)	⬇️
src/sql/src/statements/create.rs	100.00% <ø> (ø)
src/table/src/requests.rs	55.55% <ø> (ø)
src/datanode/src/sql/create.rs	89.07% <83.33%> (-0.24%)	⬇️
src/sql/src/parsers/create_parser.rs	97.08% <93.33%> (-0.23%)	⬇️
src/sql/src/statements.rs	89.58% <96.15%> (+0.33%)	⬆️
src/datanode/src/instance/grpc.rs	97.76% <100.00%> (+0.01%)	⬆️
src/datanode/src/instance/sql.rs	80.43% <100.00%> (+0.08%)	⬆️
src/frontend/src/instance/distributed.rs	92.15% <100.00%> (+0.01%)	⬆️
... and 12 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[waynexia]

And I can't find a common characteristic from queries in optimizer/filter_push_down.sql. From the naming I would expect something like EXPLAIN rather than execute those SQLs.

[killme2008]

And I can't find a common characteristic from queries in optimizer/filter_push_down.sql. From the naming I would expect something like EXPLAIN rather than execute those SQLs.

It's moved from duckdb, and EXPLAIN will be test in optimizer cases.

[waynexia]

and EXPLAIN will be test in optimizer cases.

Do you mean they will be added in the future? Maybe we can change it now, those queries have fewer means by executing themselves, and is not what the case name filter_push_down means.

[killme2008]

and EXPLAIN will be test in optimizer cases.

Do you mean they will be added in the future? Maybe we can change it now, those queries have fewer means by executing themselves, and is not what the case name filter_push_down means.

Sorry, my mistake. I meant that the duckdb has a test suite for EXPLAIN command https://github.com/duckdb/duckdb/tree/master/test/sql/explain

We'll move them later.