Repository navigation
Docs: a failed load can keep different rows on the two packages (closes #174) - #212
Merged
Merged
Conversation
…ges (closes #174) The commit-size defaults are measured per build (native 1000, JVM 10000) and stay; the bulk-loads page already explained what a failed load keeps. This adds the cross-package consequence and the way to make it identical (the same commit_every on both, or commit_every=0). No behaviour change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The commit-size defaults of
insert_many,graph_batchandcreate_verticesare measured per build (native 1000, JVM 10000, the A/B is on the bulk-loads page) and stay as they are. The page already explains what a failed load keeps; this adds one paragraph saying that the same program can therefore keep different rows on the two packages after the same failure, and how to make the outcome identical (the samecommit_everyon both, orcommit_every=0). No behaviour change.Closes #174
🤖 Generated with Claude Code