feat: support Create Table ... Like

[KKould]

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

Support: create table xxx like yyy
ref: https://dev.mysql.com/doc/refman/8.0/en/create-table-like.html

public=> CREATE TABLE t1 ( a INT, b STRING, c INT, ts timestamp TIME INDEX);
OK 0
public=> CREATE TABLE t2 LIKE t1;
OK 0
public=> DESCRIBE t2;
 Column |         Type         | Key | Null | Default | Semantic Type 
--------+----------------------+-----+------+---------+---------------
 a      | Int32                |     | YES  |         | FIELD
 b      | String               |     | YES  |         | FIELD
 c      | Int32                |     | YES  |         | FIELD
 ts     | TimestampMillisecond | PRI | NO   |         | TIMESTAMP
(4 rows)

Tips:
I was using this case: CREATE TABLE t1 ( a INT, b STRING, c INT, ts timestamp TIME INDEX); then run CREATE TABLE t2 LIKE t1;, the create_partitions_stmt method returned Some and caused the index to go out of bounds, so I did additional checks. Is this a bug? Because this table does not specify Partitions

ref: https://github.com/GreptimeTeam/greptimedb/pull/3372/files#diff-2563d4135f7e232aaec6a39204e6e9afc21801dff0c957772ce4dd7d3bd271d4R109

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.

Refer to a related PR or issue link (optional)

#2509

[codecov]

Codecov Report

Attention: Patch coverage is 72.13115% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 84.60%. Comparing base (dc205a2) to head (0d5948e).
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3372      +/-   ##
==========================================
- Coverage   85.07%   84.60%   -0.47%     
==========================================
  Files         889      889              
  Lines      146377   146454      +77     
==========================================
- Hits       124525   123906     -619     
- Misses      21852    22548     +696     

[killme2008]

Great work! Thank you. I have a few suggestions, please take a look.

[killme2008]

Looks like create table like can support if_not_exists too, just like

CREATE TABLE IF NOT EXISTS snapshot LIKE source_data;

[KKould]

In fact, I thought so at first, but I checked MySQL's Create Table ... Like and it seems that it is not supported, so I chose to keep it unified. Of course, this is up to you to decide.

ref: https://dev.mysql.com/doc/refman/8.0/en/create-table-like.html

[killme2008]

Got it. Let's leave it currently.

[KKould]

my grandmother passed away yesterday, and I will handle the review suggestions you provided in a few days

[killme2008]

my grandmother passed away yesterday, and I will handle the review suggestions you provided in a few days

Sorry to hear that. May she rest in peace.

[KKould]

It seems you didn’t notice the content in Tips. please take a look

[killme2008]

LGTM

[tisonkun]

Thanks for your contribution @KKould! Excellent patch.

I suggest you try to check out a different branch (rather than main) the next time you submit a PR so that we can avoid some subtle issues like:

$ git push
fatal: The upstream branch of your current branch does not match
the name of your current branch.  To push to the upstream branch
on the remote, use

    git push https://github.com/KKould/greptimedb.git HEAD:main

To push to the branch of the same name on the remote, use

    git push https://github.com/KKould/greptimedb.git HEAD

To choose either option permanently, see push.default in 'git help config'.

To avoid automatically configuring an upstream branch when its name
won't match the local branch, see option 'simple' of branch.autoSetupMerge
in 'git help config'.

Although we can use git push https://github.com/KKould/greptimedb.git HEAD:main as suggested, it's easy to make mistake.