Repository navigation
RAG Builder: Weaviate as a vector store - #84
Merged
Merged
Conversation
The RAG runtime, the steps and the ingestion job have had Weaviate since 2.5.0; the Builder offered pgvector and SingleStore only. - RAG_BACKENDS gets a Weaviate row, and each row now carries its default port (8080 for Weaviate) and whether the store has databases. Weaviate has none: a setup needs WEAVIATE_RAG_USER/_PW and WEAVIATE_HOST/_PORT, no WEAVIATE_DB, and records the backend's name where a database goes - never the RAGSTORE_DB a lookup would fall back to, which names another store. The Load step requires the field, and a flow with a required field left empty does not run in SAS Studio, so the flow gets it too. - The Options pane offers "RAG: offer Weaviate" (enable_weaviate), from the same list; mdb's MERGED_REPORT_LABELS has it, and the two tests that count the labels say 33 and 9. - The help text of the store says the backends carry the same chunk features and that Weaviate keeps no run history (en, de). - verify: all-keys holds every store, a RAGSTORE_DB included, and a new section saves and manifests a setup on Weaviate: host, port 8080, its name as the database, the tag, the job parameters, the Load step of the flow and the MANIFEST block of the retrieval model. - Docs: the Weaviate entries of the credential domain, the option, and what was measured live on 2026-11-10 (the custom steps from x86 SAS Viya through an ingress route, Enrich, Purge, Register Setup with a flow and its generated job, the retrieval model). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: David Weik <geekupyourlife@gmail.com>
…vice Published to maslocal and scored with the credentials in its options: status ok for three questions, the expected document first, 0.06 to 0.12 seconds in the model. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: David Weik <geekupyourlife@gmail.com>
This was referenced Nov 12, 2026
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
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
The RAG runtime, the steps and the ingestion job have had Weaviate since 2.5.0, but the RAG Builder offered only pgvector and SingleStore. This adds Weaviate to the Builder.
RAG_BACKENDSgets a Weaviate row. Each row now carries its default port (Weaviate: 8080) and whether the store has databases.WEAVIATE_RAG_USER/_PWandWEAVIATE_HOST/_PORTfrom the credential domain and needs noWEAVIATE_DB.RAGSTORE_DBa lookup would fall back to, which names another store.enable_weaviate). mdb'sMERGED_REPORT_LABELShas it, and the two tests that count the labels now say 33 and 9.RAGSTORE_*fallback.Measured live (2026-11-10, Weaviate 1.39.12 on the DGX Spark)
The custom steps ran from x86 SAS Viya (viya4-s2) through an ingress route to Weaviate's
/v1. The Builder itself was tested with its mock suite only, not on a live SAS Viya.Release note
Until the next release,
mdb package-checkshowsenable_weaviateas drift: the shipped report lacks the label. At the release, the Prompt Builder report needs one save in Visual Analytics with the new page, as in 2.4.0.Test plan
package-check --releasefails as expected before the release's package PR.npm run build. The committeddist/index.htmlis that build, byte for byte; a rebuild of unchanged main also reproduces its committed page exactly.weaviateinverify-rag. It saves and manifests a setup on Weaviate, then checks the host, port 8080, the backend's name as the database, the tag, the job parameters, the Load step of the flow and the MANIFEST block of the retrieval model.🤖 Generated with Claude Code