-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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.
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
feat: migrate transactions to sql database #2915
Conversation
nicoloboschi
commented
Jul 24, 2024
•
edited
Loading
edited
- Use transactions table on sqldb instead of duckdb
- Transactions are wrote best-effort async to avoid blocking hot path
- Ensure migrations happen at the startup
- Added file lock before acquiring duckdb connection to avoid concurrency errors
- Fixed a bug whereas all transactions and built vertex are wiped out at every startup
- Improved conccurreny in services
Pull Request Validation ReportThis comment is automatically generated by Conventional PR Whitelist Report
Result Pull request matches with one (or more) enabled whitelist criteria. Pull request validation is skipped. Last Modified at 24 Jul 24 12:26 UTC |
This pull request is automatically being deployed by Amplify Hosting (learn more). |
d6b3e58
to
a83cf84
Compare
8e37fc9
to
8b3bc3d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* feat: migrate transactions to sql database * feat: migrate transactions to sql database * feat: migrate transactions to sql database * feat: migrate transactions to sql database * feat: migrate transactions to sql database * feat: migrate transactions to sql database * [autofix.ci] apply automated fixes * remove useless * remove useless --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> (cherry picked from commit 9ac861d)