feat!: switch to new catalog/schema key #2140
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WenyXu
requested review from
MichaelScofield,
fengys1996,
paomian and
fengjiachun
and removed request for
MichaelScofield
Codecov Report
@@ Coverage Diff @@
## develop #2140 +/- ##
===========================================
- Coverage 84.88% 84.58% -0.30%
===========================================
Files 696 696
Lines 110476 110528 +52
===========================================
- Hits 93781 93495 -286
- Misses 16695 17033 +338 |
WenyXu
force-pushed
the
feat/switch-to-new-catalog-schema-key
branch
from
3458a0f
to
fcd5cb2
Compare
|
PTAL @MichaelScofield |
MichaelScofield
approved these changes
Aug 11, 2023
…ew-catalog-schema-key
paomian
pushed a commit
to paomian/greptimedb
that referenced
this pull request
Oct 19, 2023
* feat!: switch to new catalog/schema key * chore: apply suggestions from CR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
switch to new catalog/schema key
Checklist
Refer to a related PR or issue link (optional)
close #2024