feat(engine): move embedding queue from shared schema to per-engine#1
Merged
feat(engine): move embedding queue from shared schema to per-engine#1
Conversation
Remove the shared `embedding` schema (queue, queue_hist, enqueue_embedding, claim_batch) from bootstrap and relocate embedding infrastructure into a per-engine migration (005_embedding_queue.sql). Each engine schema now owns its own embedding_queue table with FK ON DELETE CASCADE, enqueue_embedding() trigger function, and claim_embedding_batch() for the worker. This enables clean DROP SCHEMA CASCADE, pg_dump portability, and per-engine QoS control. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Remove the shared
embeddingschema (queue, queue_hist, enqueue_embedding, claim_batch) from bootstrap and relocate embedding infrastructure into a per-engine migration (005_embedding_queue.sql). Each engine schema now owns its own embedding_queue table with FK ON DELETE CASCADE, enqueue_embedding() trigger function, and claim_embedding_batch() for the worker. This enables clean DROP SCHEMA CASCADE, pg_dump portability, and per-engine QoS control.