Skip to content

Update lab1.md for test commands in makefile #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update lab1.md for test commands in makefile #4

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
036e9c8
Update lab1.md
Cerdore Apr 29, 2022
1e0740b
Update lab1.md
Cerdore May 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions tinykv/doc/lab1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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

Expand All @@ -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.
Expand All @@ -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.