This is an automated email from the ASF dual-hosted git repository.
hulk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/kvrocks-website.git
The following commit(s) were added to refs/heads/main by this push:
new 88425c7 Fix the subkey index for Bitmap structure in document (#194)
88425c7 is described below
commit 88425c7a94bcb9b07bfcbfb3561fe69023049625
Author: mwish <[email protected]>
AuthorDate: Tue Feb 6 10:00:52 2024 +0800
Fix the subkey index for Bitmap structure in document (#194)
---
community/data-structure-on-rocksdb.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/community/data-structure-on-rocksdb.md
b/community/data-structure-on-rocksdb.md
index ab047d9..9591c0e 100644
--- a/community/data-structure-on-rocksdb.md
+++ b/community/data-structure-on-rocksdb.md
@@ -208,7 +208,7 @@ key|version|index => | fragment |
+---------------+
```
-When the user requests to get it of position P, Kvrocks would first fetch the
metadata with bitmap's key and calculate the index of the fragment with bit
position, then fetch the bitmap fragment with composed key and find the bit in
fragment offset. For example, `getbit bitmap 8193`, the fragment index is `1`
(8193/8192) and subkey is `bitmap|1|1` (when the version is 1), then fetch the
subkey from RocksDB and check if the bit of offset `1`(8193%8192) is set or not.
+When the user requests to get it of position P, Kvrocks would first fetch the
metadata with bitmap's key and calculate the index of the fragment with bit
position, then fetch the bitmap fragment with composed key and find the bit in
fragment offset. For example, `getbit bitmap 8193`, the fragment index is `1`
(8193/8192) and subkey is `bitmap|1|1024` (when the version is 1, and fragment
index is `1`, kvrocks will use `1 * 1024` as the index key), then fetch the
subkey from RocksDB and ch [...]
## SortedInt
