Fix incorrect used_db_size value #204
Merged
karelrooted merged 1 commit intoapache:unstablefrom Mar 16, 2021
Merged
Conversation
Member
|
Seems the commit message didn't match the PR changes. It should be: |
…d the key range GetApproximateSizes needs the start/end key of the corresponding column family. But we always use the metadata column family to find the start/end key range.
karelrooted
force-pushed
the
fix/used-db-size-not-include-default-cf
branch
from
9f30165 to
9079a05
Compare
karelrooted
changed the title
git-hulk
approved these changes
Mar 16, 2021
ShooterIT
approved these changes
Mar 16, 2021
git-hulk
approved these changes
Mar 16, 2021
Merged
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix incorrect used_db_size value which always uses the same cf to find the key range
GetApproximateSizes needs the start/end key of the corresponding column family.
But we always use the metadata column family to find the start/end key range.