Skip to content

fix(loader): transfer writes the tenant DuckDB under tenants/<tenant>/#201

Merged
jrosskopf merged 1 commit into
mainfrom
fix/loader-transfer-tenant-path
Jun 24, 2026
Merged

fix(loader): transfer writes the tenant DuckDB under tenants/<tenant>/#201
jrosskopf merged 1 commit into
mainfrom
fix/loader-transfer-tenant-path

Conversation

@jrosskopf

Copy link
Copy Markdown
Contributor

escurel-server keeps each tenant DB at <data_dir>/tenants/<tenant>/escurel.duckdb, but transfer opened it at the data-dir root — so rows landed in a stray DB the server never reads (blobs/overlays were correct). Fixed to nest under tenants/<tenant>/; capstone test updated. Found transferring a 203-doc Gemini corpus into the herkules tenant.

🤖 Generated with Claude Code

escurel-server keeps each tenant's DuckDB at `<data_dir>/tenants/<tenant>/
escurel.duckdb` (config.rs), and the FsStore keys blobs/overlays under the same
prefix. But `transfer` opened the DB at `<data_dir>/escurel.duckdb` (root) — so
merging into a real escurel data dir wrote the rows to a stray root DB the server
never reads, while blobs/overlays correctly landed under tenants/<tenant>/. The
capstone test used a self-consistent (root) layout, so it didn't catch this.

Open the DB at `to/tenants/<tenant>/escurel.duckdb` (create the dir), matching
the server. Capstone test updated to assert the tenant-subdir path.

Found while transferring a 203-doc Gemini corpus into the herkules tenant: the
server saw 0 new instances until the path was corrected.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@jrosskopf jrosskopf merged commit 342a8a8 into main Jun 24, 2026
@jrosskopf jrosskopf deleted the fix/loader-transfer-tenant-path branch June 24, 2026 07:52
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