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.

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
merged 21 commits into from
Nov 2, 2023
Merged

Conversation

sreuland
Copy link
Contributor

@sreuland sreuland commented Nov 1, 2023

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with name of package that is most changed in the PR, ex.
    services/friendbot, or all or doc if the changes are broad or impact many
    packages.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated any docs (developer docs, .md
    files, etc... affected by this change). Take a look in the docs folder for a given service,
    like this one.

Release planning

  • I've updated the relevant CHANGELOG (here for Horizon) if
    needed with deprecations, added features, breaking changes, and DB schema changes.
  • I've decided if this PR requires a new major/minor version according to
    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 loaders

Why

Closes #4909

Known limitations

tamirms and others added 21 commits July 5, 2023 09:47
…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)
… claimable balances, liquidity pools, and participants tables (#4971)
…ctions, and operations processors to support new ingestion data flow (#5004)
…, trades, and claimable balances processors to support new ingestion data flow (#5025)
Merge latest master to ingestion-next
merge latest master back to ingestion-next
@sreuland
Copy link
Contributor Author

sreuland commented Nov 1, 2023

@tamirms , just to confirm, I will squash this to master, but wanted to verify first, let me know if would prefer different, thanks!

@tamirms
Copy link
Contributor

tamirms commented Nov 2, 2023

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 tamirms merged commit 4670509 into master Nov 2, 2023
26 checks passed
@tamirms tamirms deleted the ingestion-next branch November 2, 2023 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor ingestion data-flow
2 participants