Skip to content
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

Jump to bottom

Correct a Typo #3

Merged
merged 1 commit into from
Apr 2, 2024
Merged

Correct a Typo #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ Complete the following steps:
```

2. Call the `load_denormalized.sh` file using the `parallel` program from within the `load_tweets_parallel.sh` script.
You know you've completed this step correctly if the `check-answers.sh` script passes and the test badge turns green.
You know you've completed this step correctly if the `check_answers.sh` script passes and the test badge turns green.

#### Normalized Data (unbatched)

Expand All @@ -113,7 +113,7 @@ so even when run in parallel it is still slower than the batched code.
Parallel loading of the batched data will fail due to deadlocks.
These deadlocks will cause some of your parallel loading processes to crash.
So all the data will not get inserted,
and you will fail the `check-answers.sh` tests.
and you will fail the `check_answers.sh` tests.

There are two possible ways to fix this.
The most naive method is to catch the exceptions generated by the deadlocks in python and repeat the failed queries.
Expand Down