feat(bulk): add error logging to bulk loader#9601
Merged
matthewmcneely merged 2 commits intomainfrom Feb 18, 2026
Merged
Conversation
shiva-istari
approved these changes
Feb 16, 2026
This file contains hidden or 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
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.
Description
This PR adds error logging to the bulk loader. Prior to these changes, error handling in bulk loading allowed for only ignoring errors or stopping the load upon any error. These changes allow for errors to be logged to a file so that the entire bulk loading operation does not have to be an "all or nothing" exercise -- important for loads that can take hours to complete.
The new flags look like this:
The existing --ignore_errors flag is required. The location of the error log can be specfied, the default is
bulk_errors.log.Checklist
Conventional Commits syntax, leading
with
fix:,feat:,chore:,ci:, etc.docs repo staged and linked here. This process can
be simplified by going to the public docs site and clicking the
"Edit this page" button at the bottom of page(s) relevant to your changes. Ensure that you
indicate in the PR that this is an unreleased feature so that it does not get merged into
the main docs prematurely.