feat(fuzz): enable create-if-not-exists option

[CookiePieWw]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

Enable the existing IF NOT EXISTS option in fuzz test.

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR does not require documentation updates.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.12%. Comparing base (7e56bf2) to head (34e8254).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3732      +/-   ##
==========================================
- Coverage   85.42%   85.12%   -0.31%     
==========================================
  Files         966      966              
  Lines      162097   162097              
==========================================
- Hits       138472   137984     -488     
- Misses      23625    24113     +488     

[tisonkun]

Cool! Thank you :D

[WenyXu]

@CookiePieWw Thanks! BTW, we introduced a new engine for metric scenarios(called metric engine). Would you like to add some fuzz tests for this new engine?

The metric engine's RFC: https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2023-07-10-metric-engine.md

The following tests show how we create tables in the metric engine:

greptimedb/tests/cases/standalone/common/create/create_metric_table.sql

Lines 1 to 36 in 7e56bf2

	CREATE TABLE phy (ts timestamp time index, val double) engine=metric with ("physical_metric_table" = "");
	SHOW TABLES;
	DESC TABLE phy;
	CREATE TABLE t1 (ts timestamp time index, val double, host string primary key) engine = metric with ("on_physical_table" = "phy");
	CREATE TABLE t2 (ts timestamp time index, job string primary key, val double) engine = metric with ("on_physical_table" = "phy");
	SELECT table_catalog, table_schema, table_name, table_type, engine FROM information_schema.tables WHERE engine = 'metric' order by table_name;
	DESC TABLE phy;
	DESC TABLE t1;
	DESC TABLE t2;
	-- should be failed
	-- SQLNESS REPLACE (region\s\d+\(\d+\,\s\d+\)) region
	DROP TABLE phy;
	-- metadata should be restored
	DESC TABLE phy;
	DROP TABLE t1;
	DROP TABLE t2;
	DROP TABLE phy;
	-- create one with other primary keys
	CREATE TABLE phy2 (ts timestamp time index, val double, abc string, def string, primary key (abc, def)) engine=metric with ("physical_metric_table" = "");
	DESC TABLE phy2;
	DROP TABLE phy2;

cc @waynexia

[CookiePieWw]

BTW, we introduced a new engine for metric scenarios(called metric engine). Would you like to add some fuzz tests for this new engine?

Sure, I'll work on it later 😊.

[WenyXu]

BTW, we introduced a new engine for metric scenarios(called metric engine). Would you like to add some fuzz tests for this new engine?

Thanks! I will create an issue for this feature