You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Index no search document for an entity without a database row #61
arocapi requires a database row for every search hit, and otherwise drops the hit while still counting it in total and the facets. The search indexer reads the crate's rows from the database (by meta.crateId) and indexes only the entities that have one, logging each one it skips. A search's total then matches the hits a user can page through.
Ships on the one #52 branch and PR, as its own commit. See #52 for the decisions behind it.
Acceptance criteria
An entity whose database row fails to be written gets no search document, and the skip is logged with the crate and entity ids
A search's total and facet counts match the hits returned when such a failure occurred
Implemented in #63. Changed from the original ticket: rather than being handed the ids the database indexer wrote, the search indexer reads the crate's rows itself (by meta.crateId), which also gives each document its rootCollection and works when only the search index is rebuilt. When a crate has no rows at all, the skip is logged once for the crate. The body is updated to match.
Activity
johnf commentedon Nov 4, 2026
Implemented in #63. Changed from the original ticket: rather than being handed the ids the database indexer wrote, the search indexer reads the crate's rows itself (by
meta.crateId), which also gives each document itsrootCollectionand works when only the search index is rebuilt. When a crate has no rows at all, the skip is logged once for the crate. The body is updated to match.