-
Notifications
You must be signed in to change notification settings - Fork 500
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
horizon/services/ingest: merge ingestion-next to master #5101
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…4916) * Add batch insert builder which uses COPY to insert rows * Update support/db/fast_batch_insert_builder.go Co-authored-by: George <[email protected]> * Update fast_batch_insert_builder_test.go --------- Co-authored-by: George <[email protected]>
…insert transactions into the history_transactions (#4950)
…insert operations into history_operations (#4952)
… claimable balances, liquidity pools, and participants tables (#4971)
… trades and effects (#4975)
…ctions, and operations processors to support new ingestion data flow (#5004)
…uture account ids (#5015)
…claimable balances, and liquidity pools (#5019)
…ocessors to support new ingestion data flow (#5024)
…, trades, and claimable balances processors to support new ingestion data flow (#5025)
…or to support new ingestion data flow (#5028)
Merge latest master to ingestion-next
merge latest master back to ingestion-next
@tamirms , just to confirm, I will squash this to master, but wanted to verify first, let me know if would prefer different, thanks! |
I think it's better to merge rather than squash so that you can track the code back to the relevant PR using git blame |
tamirms
approved these changes
Nov 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
PR Structure
otherwise).
services/friendbot
, orall
ordoc
if the changes are broad or impact manypackages.
Thoroughness
.md
files, etc... affected by this change). Take a look in the
docs
folder for a given service,like this one.
Release planning
needed with deprecations, added features, breaking changes, and DB schema changes.
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
merging the feature branch
ingestion-next
which has new ingestion performance updates with fast batch builder and loadersWhy
Closes #4909
Known limitations