feat: support custom storage for every table(initial)

[NiwakaDev]

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

This PR addresses a part of #919.

Here's an example of using this feature.

create table foo(a string, ts TIMESTAMP TIME INDEX, ~)with(storage='Gcs');

Note that this PR doesn't implement:

• custom storage for region failover.
• custom storage for file engine.

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)

Not close #919 yet.

[NiwakaDev]

I rebased the develop branch, and then rustc says:

error: use of deprecated method `chrono::DateTime::<Tz>::timestamp_nanos`: use `timestamp_nanos_opt()` instead
  --> src/common/time/src/timestamp.rs:66:41
   |
66 |             TimeUnit::Nanosecond => now.timestamp_nanos(),
   |                                         ^^^^^^^^^^^^^^^
   |
   = note: `-D deprecated` implied by `-D warnings`

error: use of deprecated method `chrono::TimeZone::datetime_from_str`: use `DateTime::parse_from_str` instead
   --> src/common/time/src/timestamp.rs:301:29
    |
301 |         if let Ok(ts) = Utc.datetime_from_str(s, "%Y-%m-%d %H:%M:%S%.fZ") {
    |                             ^^^^^^^^^^^^^^^^^

[evenyag]

@NiwakaDev Maybe caused by a newer opendal version. Our Cargo.lock file uses opendal 0.40.0. Did you try using git merge instead of git rebase?

[codecov]

Codecov Report

Merging #2605 (e3bd4ff) into develop (d9e7b89) will decrease coverage by 0.53%.
Report is 4 commits behind head on develop.
The diff coverage is 92.52%.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2605      +/-   ##
===========================================
- Coverage    85.33%   84.81%   -0.53%     
===========================================
  Files          737      739       +2     
  Lines       118042   118707     +665     
===========================================
- Hits        100736   100683      -53     
- Misses       17306    18024     +718     

[NiwakaDev]

greptimedb/.github/workflows/develop.yml

Lines 178 to 184 in 3217b56

	GT_S3_BUCKET: ${{ secrets.S3_BUCKET }}
	GT_S3_ACCESS_KEY_ID: ${{ secrets.S3_ACCESS_KEY_ID }}
	GT_S3_ACCESS_KEY: ${{ secrets.S3_ACCESS_KEY }}
	GT_S3_REGION: ${{ secrets.S3_REGION }}
	UNITTEST_LOG_DIR: "__unittest_logs"
	- name: Codecov upload
	uses: codecov/codecov-action@v2

Settings for S3 reside, but it seems like bucket is empty.

[evenyag]

The S3_BUCKET is only available in this repo's secrets. A PR from a forked repo can't get this secret. So we run the test in the CI after the PR is merged.

[evenyag]

This feature impacts many modules and contains breaking changes. I'd like to merge it gradually (in several PRs) so we can review and test it carefully. Could you please separate it into smaller PRs? e.g.

• A PR to add the ObjectStoreManager
• A PR to support the ObjectStoreManager in mito2 (Now the manager only contains one object store)
• Support specifying storage in SQL and some tests
• More tests (To address todos in this PR)

[evenyag]

This is a breaking change. storage.store is a little odd. We'd better find out a new name or revisit the storage config later.

[NiwakaDev]

This feature impacts many modules and contains breaking changes. I'd like to merge it gradually (in several PRs) so we can review and test it carefully. Could you please separate it into smaller PRs?

Sorry for submitting the large PR. Your point is correct😅. I opened a new PR(#2621), and please review it.