Repository navigation
2.5.0 Weaviate as a third RAG vector store; mdb runs with typer 0.29
Weaviate (1.33 or newer) is a third vector store for RAG, and mdb runs again with typer 0.29, with which every mdb command failed.
Upgrading from 2.4.5
Steps 1 and 2 are for every site; step 3 only where it applies.
- Update the checkout to 2.5.0 and reinstall the CLI:
pip install -e "Model-Definition-Builder/cli[viya]". The fix comes with the checkout; the reinstall brings the boundtyper<0.30. mdb builders-importand reload the Prompt Builder report, then runmdb check. The import brings the RAG steps,rag_coreand the ingestion job with Weaviate, and the release stamp of 2.5.0;mdb checkwrites the page of the release back into Start Here.- Only where RAG should store its chunks in Weaviate: add
WEAVIATE_RAG_USERandWEAVIATE_RAG_PW(the API key) to the credentials, as for the other stores (Managing Credentials), and choose Weaviate under Runtime in the RAG steps (Weaviate).
Added
- Weaviate backend.
rag_core.adapters.weaviatetalks to Weaviate's REST and GraphQL API withrequests- no driver to install - and carries the same chunk lineage as pgvector and SingleStore: retire, restore, as-of reads, prune, erasure. Cutover moves a collection alias. The governance DDL is the create-collection request, saved asvector-store-ddl.json. The manifested retrieval model reads Weaviate over GraphQL. Weaviate keeps no run history (rag_runs,rag_doc_events,rag_configsare SQL): the Load step and the ingestion job say so in the log and publish nothing. Hybrid search waits for all backends. - The RAG steps offer Weaviate. RAG - Load Vector Store, Retrieve Context and Purge Documents 1.5 list it under Runtime, with the TLS control; Register Setup 1.5 names the port and the JSON DDL. The database name is not used by Weaviate.
Changed
mdb package-check: a new manifest entry is drift. A folder, file, step or job definition the manifest gains is adrift:line until the next export, so a pull request can add one without the package;--releasestill refuses it.
Fixed
- mdb runs with typer 0.29. typer 0.29.0 (2026-11-09) gives a parameter an annotation instead of click's type, and every mdb command ended with
AttributeError: 'TyperArgument' object has no attribute 'type'. mdb now reads either, and requirestyper<0.30: a newer typer comes in when the tests pass on it. A maintainer checks for one once a month.