From 036e9c865d77cf346b69071cb1a87583111e3903 Mon Sep 17 00:00:00 2001 From: Cerdore Date: Fri, 29 Apr 2022 14:05:35 +0800 Subject: [PATCH 1/2] Update lab1.md Follow . /tinykv/makefile to adjust the make parameters --- tinykv/doc/lab1.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tinykv/doc/lab1.md b/tinykv/doc/lab1.md index ecf45ca..3678d6c 100644 --- a/tinykv/doc/lab1.md +++ b/tinykv/doc/lab1.md @@ -121,7 +121,7 @@ Things to note: - `CommitTS` is the expected commit timestamp for one record. - Consider the read write conflicts processing. -After finish these two parts, run `make lab2P1` to check if all the tests are passsed. +After finish these two parts, run `make lab1P1` to check if all the tests are passsed. #### Implement the `Rollback` and `CheckTxnStatus` Commands @@ -130,7 +130,7 @@ After finish these two parts, run `make lab2P1` to check if all the tests are pa ``` // YOUR CODE HERE (lab1). ``` -After finish these parts, run `make lab2P2` to check if all the tests are passed. Things to note: +After finish these parts, run `make lab1P2` to check if all the tests are passed. Things to note: - Consider the situation query lock dose not exist. - There could be duplicate requests as these commands are sent through rpc requests from tinysql server. - There are three different response actions in the `CheckTxnStatusResponse`. `Action_TTLExpireRollback` means the target lock is rolled back as it has expired and `Action_LockNotExistRollback` means the target lock does not exist and the rollback record is written. @@ -145,8 +145,8 @@ These code parts are marked with: // YOUR CODE HERE (lab1). ``` -After finish these parts, run `make lab2P3` to check if all the tests are passed. Things to note: +After finish these parts, run `make lab1P3` to check if all the tests are passed. Things to note: - The transaction status has been decided in the input request parameters. - The `rollbackKey` and `commitKey` could be helpful. -After all the commands and tests are finished, run `make lab2P4` to check if tests in another suite are passed. In the next lab we'll try to implement the transaction coordinator part for percolator protocol in the `tinysql` server, and all these commands will be used. +After all the commands and tests are finished, run `make lab1P4` to check if tests in another suite are passed. In the next lab we'll try to implement the transaction coordinator part for percolator protocol in the `tinysql` server, and all these commands will be used. From 1e0740b2346488af6014a227c38b53f3a212a77b Mon Sep 17 00:00:00 2001 From: Cerdore Date: Sun, 1 May 2022 09:57:07 +0800 Subject: [PATCH 2/2] Update lab1.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Modify the title ‘lab2’ as well as the prompt to complete lab1P0 --- tinykv/doc/lab1.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tinykv/doc/lab1.md b/tinykv/doc/lab1.md index 3678d6c..f7b1bcb 100644 --- a/tinykv/doc/lab1.md +++ b/tinykv/doc/lab1.md @@ -67,9 +67,9 @@ These conflict processing is called `Resolve` in `tinysql/tinykv` clusters. Once by the concurrent transaction requests from other `tinysql` servers. -## LAB2 +## LAB1 -We're going to implement the above interface and their processing logic in tinykv server. +Before starting this section, please complete [lab1P0](#implement-the-core-interfaces-of-standalongstorage) above. We're going to implement the above interface and their processing logic in tinykv server. ### The Code