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
Adds read-only serving of prebuilt DuckDB vocabulary/graph files and separate DuckDBVSS embedding stores through groundworkers[duckdb].
Configuration and setup support the two-file topology, reject missing or colocated files, and prevent maintenance writes against served assets. Vocabulary lookup, normalized search, ancestry, relationships and embedding retrieval remain available; PostgreSQL full-text search is reported as unavailable on DuckDB.
Graph preparation now uses omop-graph’s packaged classification defaults. Removes Groundworkers’ obsolete CSV copies while preserving explicit custom-directory overrides.
Requires oa-configurator ≥2.1, omop-alchemy ≥3, omop-graph ≥4 and omop-emb ≥3.1. Includes relationship-traversal hardening and integrates backend guidance into the existing documentation.
Production asset building, manifests and deployment validation remain separate follow-on work.
Adds read-only DuckDB support for prebuilt vocabulary/graph files and separate embedding stores. Graph preparation now uses omop-graph’s packaged classification defaults, addressing #16.
Changes:
Adds DuckDB dependencies, configuration, read-only connection policies, and maintenance guards.
Supports DuckDB normalized search and strengthens bounded relationship traversal.
Adds runtime and packaging tests, setup coverage, and deployment documentation.
File
Description
uv.lock
Locks upgraded OMOP packages and DuckDB dependencies.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Hard-linked embedding paths bypass file-separation checks, allowing initialization to open a writer against the CDM itself, and existing DuckDB stores are incorrectly displayed as unconfigured.
This setup check also accepts a hard link to the CDM: the resolved filenames differ even though Path.samefile() returns true. The wizard can therefore apply a configuration that violates the separate-file requirement. Check physical file identity for existing paths, while keeping path equality for new targets.
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
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.
Summary
Adds read-only serving of prebuilt DuckDB vocabulary/graph files and separate DuckDBVSS embedding stores through
groundworkers[duckdb].Configuration and setup support the two-file topology, reject missing or colocated files, and prevent maintenance writes against served assets. Vocabulary lookup, normalized search, ancestry, relationships and embedding retrieval remain available; PostgreSQL full-text search is reported as unavailable on DuckDB.
Graph preparation now uses omop-graph’s packaged classification defaults. Removes Groundworkers’ obsolete CSV copies while preserving explicit custom-directory overrides.
Requires oa-configurator ≥2.1, omop-alchemy ≥3, omop-graph ≥4 and omop-emb ≥3.1. Includes relationship-traversal hardening and integrates backend guidance into the existing documentation.
Production asset building, manifests and deployment validation remain separate follow-on work.
Closes #16
Checklist
breaking,feature,fix,dependencies, orchore)uv run pytest -q)uv run ruff check .)