Repository navigation
Avoid full database scans during imports - #25
Merged
Merged
Conversation
Codex-Session: docs/ai-logs/sessions/2026-09-08-import-prefix-scans.md
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
1 participant
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.
Large imports scanned and decoded every resource for each imported record when checking for obsolete nested resources and legacy drives. Use Atomic Data's indexed subject-prefix iterator for those lookups, and for scoped reads/listing/deletion, while preserving the same cleanup boundaries.
Updates atomic_lib to the commit providing the indexed API. This supports ontola/atomic-server#1383.
Validation: all 51 library tests pass; cargo clippy --all-targets -- -D warnings passes; the real AtomicServer OAuth import integration test passes with this change. The user approved the patch and publication.