feat: atomic metadata #2366
Merged
feat: atomic metadata #2366
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2366 +/- ##
===========================================
- Coverage 77.55% 77.49% -0.07%
===========================================
Files 716 715 -1
Lines 113722 113674 -48
===========================================
- Hits 88202 88093 -109
- Misses 25520 25581 +61 |
fengjiachun
force-pushed
the
feat/atomic-metadata
branch
from
03a2400 to
3ee369b
Compare
WenyXu
approved these changes
Sep 13, 2023
|
@MichaelScofield PTAL |
MichaelScofield
approved these changes
Sep 13, 2023
paomian
pushed a commit
to paomian/greptimedb
that referenced
this pull request
Oct 19, 2023
* feat: atomic creating metadata * chore: exist exists * chore: license header * chore: weny never say that * feat: add put_conditionally to kv_backend
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?
metadata_serviceChecklist
Refer to a related PR or issue link (optional)