maokaihe/mini_lsm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix minor mistake in W3D6 writeup (#69)

Browse Source
This commit is contained in:
Yue Yin
2024-03-24 15:24:38 -04:00
committed by GitHub
parent afe6c9549d
commit bcaab6f706
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
mini-lsm-book/src/week3-06-serializable.md
View File

@@ -80,7 +80,7 @@ If the database starts with an initial state of `a=1,b=2`, we should get either
txn1: len(scan(..)) = 2 txn1: len(scan(..)) = 2
txn2: len(scan(..)) = 2 txn2: len(scan(..)) = 2
txn1: put key1 = 2, commit, read set = {a, b}, write set = {key1} txn1: put key1 = 2, commit, read set = {a, b}, write set = {key1}
txn2: put key2 = 2, commit, read set = {a, b}, write set = {key1} txn2: put key2 = 2, commit, read set = {a, b}, write set = {key2}
``` ```
This passes our serializable validation and does not correspond to any serial order of execution! Therefore, a fully-working serializable validation will need to track key ranges, and using key hashes can accelerate the serializable check if only `get` is called. Please refer to the bonus tasks on how you can implement serializable checks correctly. This passes our serializable validation and does not correspond to any serial order of execution! Therefore, a fully-working serializable validation will need to track key ranges, and using key hashes can accelerate the serializable check if only `get` is called. Please refer to the bonus tasks on how you can implement serializable checks correctly.