Repository navigation
docs: a crate that clashes with another fails its index job - #93
Merged
Merged
Conversation
This was referenced Nov 17, 2026
Closed
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.
Updates ADR 0006 ("A shared entity's row is one crate's copy"). Before, a crate describing a collection, object or file that another crate already holds had that one entity refused and everything else indexed. Now the crate's index job fails.
Decided while writing Spec: indexer redesign. The previous wording made a clash the only data error that didn't fail its job, which conflicted with "Progress and failure reporting for index runs" (#87): there, any error fails the job, so an indexed version always means the whole crate is indexed. It also left the clash visible only in the log. A failed job shows on the admin pages, with an error naming both crates.
The cost: the second crate can't be searched until its data is fixed. "How shared entities are stored and deleted" (#72) had rejected refusing the whole crate, and this reverses that one point.