Skip to content

docs: a crate that clashes with another fails its index job - #93

Merged
johnf merged 1 commit into
mainfrom
docs/clash-fails-the-job
Nov 17, 2026
Merged

johnf merged 1 commit into
mainfrom
docs/clash-fails-the-job

Conversation

@johnf

@johnf johnf commented Nov 17, 2026

Copy link
Copy Markdown
Collaborator

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.

@johnf
johnf merged commit e424557 into main Nov 17, 2026
5 checks passed
@johnf
johnf deleted the docs/clash-fails-the-job branch November 17, 2026 04:26
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.

1 participant