Import: run on a fresh store, and put blobs in the imported blob store (2026.x backport of #491's fixes) #520

Merged
jcoffey-dev merged 1 commits from fix/import-fresh-store-2026 into release/2026 2026-11-21 01:30:39 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 3958f5f17e Import: run on a fresh store, and put blobs in the imported blob store
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 9m5s
Backported from 27.1 (#491), the two import fixes only; the S3 export and
store-check command stay on 27.1.

Fixed
- An import into a fresh store refused to run: every start writes the
  fork's subspace (where the blob store is, permission grants, the log
  files' setting), the import's own start too, and the import took that
  for data. Since the blob store change (#333): 2026.11.9.1. The fork's
  subspace is no longer counted; its records are keyed values an import
  sets over. The store test now imports over a start-up record, and fails
  without this.
- An import wrote the blobs into the data store, the empty store's blob
  store, even when the imported settings name another (S3, say): the
  restored server then found none of them. Blobs are imported last, into
  the blob store the imported x:BlobStore names.

Tested: store tests pass on SQLite and RocksDB; without the first fix the
store test exits at the import's refusal.
2026-11-20 18:21:09 -07:00