dbt-vectorize 0.1.11

dbt + Rust vectorization runner for pgvector

dbt-vectorize

Turn dbt models into pgvector-backed semantic indexes. Build embeddings from dbt models and query them with one command.

Quick example

Define a dbt model:

{{ config(
    materialized='vector_index',
    vector_db='pgvector',
    index_name='knowledge_base',
    unique_key='doc_id',
    text_column='text',
    dimensions=1536
) }}

select
  doc_id,
  body as text,
  source,
  created_at
from {{ ref('staging_docs') }}

Build the index:

dbt-vectorize build --select my_model

Search embeds the query and returns the closest rows from Postgres using pgvector.:

dbt-vectorize search \
  --select my_model \
  --query "oauth callback issues" \
  --top-k 5

Example output

Top 3 results from knowledge_base:

1. OAuth redirect failed due to invalid callback URL
2. Callback mismatch error in OAuth flow
3. Auth token expired during redirect

What it does

• Define vectorized datasets directly in dbt models
• Generate embeddings (Rust, no Python required)
• Store vectors in Postgres using pgvector
• Support incremental embedding (only new/updated rows)
• Search data using semantic similarity from CLI

Conceptually:

dbt model → dbt-vectorize → Postgres (pgvector) → search

How it works

1. Define a dbt model with materialized='vector_index'.
2. Run dbt-vectorize build --select ....
3. Run dbt-vectorize search --select ... --query ....

Under the hood:

• dbt builds the source dataset.
• embeddings are generated and upserted into pgvector.
• search embeds the query and performs nearest-neighbor lookup in Postgres.

Why

Embedding pipelines are usually split across dbt, Python scripts, and external jobs.

dbt-vectorize keeps that workflow closer to dbt:

• define once in dbt
• build with one command
• search using the same dataset

This makes vector search feel like a natural extension of your data models.

Status

Early but usable. Focused on Postgres + pgvector first.

Use via packages.yml (recommended for Jupyter/other dbt projects)

You do not need to copy macros/ manually.

Fast path (one command inside your dbt project root):

dbt-vectorize init --project-dir . --revision v0.1.11

init updates/creates packages.yml and runs dbt deps.

In your consumer dbt project, add packages.yml:

packages:
  - git: "https://github.com/kraftaa/dbt-vector.git"
    revision: "v0.1.11"

Reference file in this repo: examples/consumer/packages.yml.

Then install package macros/materializations:

dbt deps

If you already have packages.yml, init preserves existing package entries and only adds/updates the dbt-vector entry.

After dbt deps, materialized='vector_index' is available in your models.

Minimal files needed in Jupyter pod:

• dbt_project.yml
• profiles.yml
• models/*.sql (your vector models)
• packages.yml (snippet above)

Prerequisites

dbt-vectorize does not vendor dbt. It uses whatever dbt binary you point it to (DBT=...) or find on PATH.

Verify your existing dbt + adapter:

dbt --version

You should see a plugin like postgres under "Plugins".

If you do not have dbt + postgres adapter installed:

python -m pip install "dbt-core~=1.9" "dbt-postgres~=1.9"

You also need pgvector available in Postgres:

• install the extension package on the Postgres server (vector.control must exist on that server)
• enable it in each database you want to use

CREATE EXTENSION IF NOT EXISTS vector;

(pgvector is the project name; the SQL extension name is vector.)

Repo layout

• dbt_project.yml – declares this as a dbt package and exposes macros.
• macros/materializations/vector_index.sql – Jinja materialization scaffold (pgvector first, adapters dispatchable).
• macros/adapters/vector_index_pgvector.sql – pgvector adapter macro that creates/loads the target table.
• bin/vectorize – orchestration command that runs dbt and then Rust embedding.
• rust/embedding_engine – Rust crate and pg_embedder binary used for embedding generation/upsert.

Next steps (MVP path)

1. Harden Rust embedding provider support (OpenAI/Bedrock/local ONNX) with better diagnostics and retries. ⏳
2. Expand adapter macros beyond pgvector (Pinecone/Qdrant). ⏳
3. Add end-to-end integration tests for dbt + pgvector + pg_embedder. ⏳
4. Publish package docs and a reproducible quickstart. ⏳

Example model (current)

{{ config(
    materialized='vector_index',
    vector_db='pgvector',
    index_name='knowledge_base',
    embedding_model='text-embedding-3-small',
    dimensions=(env_var('EMBED_DIMS', 1536) | int),
    metadata_columns=['source', 'created_at', 'doc_id']
) }}

select
    doc_id,
    chunk_text as text,
    source,
    created_at
from {{ ref('staging_documents') }}
where is_active = true

Running dbt-vectorize build --select vector_knowledge_base should:

• fetch incremental rows
• generate embeddings via Rust engine
• upsert to pgvector (or Pinecone/Qdrant via adapters)
• emit metrics (processed, failed, latency) and freshness tests

Run locally (preferred: existing local Postgres)

1. Ensure Postgres is running, reachable (PGHOST/PGPORT/PGUSER/PGDATABASE), and has vector enabled:

CREATE EXTENSION IF NOT EXISTS vector;

2. Choose a provider and matching dimensions:

# Local ONNX (MiniLM, 384 dims)
EMBED_PROVIDER=local
EMBED_MODEL=sentence-transformers/all-MiniLM-L6-v2
EMBED_LOCAL_MODEL_PATH=$PWD/ml_model   # contains model.onnx + tokenizer.json
EMBED_DIMS=384

# OpenAI
EMBED_PROVIDER=openai
EMBED_MODEL=text-embedding-3-small
EMBED_DIMS=1536   # or a smaller dim if you request it from OpenAI

# Bedrock Titan v2 (defaults)
EMBED_PROVIDER=bedrock
EMBED_MODEL=amazon.titan-embed-text-v2:0
EMBED_DIMS=1024   # or 512/256 if you override

All environment variables

You can set these in shell env vars or in .env.vectorize (see .env.vectorize.example).

Variable	Purpose	Default
DBT	dbt executable path	dbt
PROFILE_DIR	dbt profiles directory	current dir
PROJECT_DIR	dbt project directory	current dir
PROFILE	dbt profile name	default
TARGET	dbt target name	from profile
SELECT_MODEL	default model selector (compat runner)	vector_knowledge_base
PGHOST PGPORT PGUSER PGPASSWORD PGDATABASE	Postgres connection	localhost:5432/postgres
SCHEMA	target schema	public
INDEX_NAME	target index/table name	knowledge_base
EMBED_PROVIDER	embedding provider (local/openai/bedrock)	local
EMBED_MODEL	model identifier for provider	provider-specific
EMBED_DIMS	vector dimensions (must match table/model)	1536
EMBED_LOCAL_MODEL_PATH	local ONNX model dir (model.onnx, tokenizer.json)	unset
OPENAI_API_KEY	OpenAI API key (required for openai)	unset
OPENAI_EMBED_URL	OpenAI-compatible embeddings endpoint override	OpenAI default URL
EMBED_DB_BATCH_SIZE	rows per DB read/write batch	1000
EMBED_MAX_BATCH	texts per provider request/batch	128
EMBED_RETRIES	retry attempts	3
EMBED_TIMEOUT_SECS	provider request timeout seconds	60
EMBED_MAX_LEN	local tokenizer max sequence length	256
EMBED_LIMIT	debug cap on embedded rows	unset
EMBED_KEEP_SOURCE	keep __vector_src after embedding (1/true)	false
EMBED_LOG_BATCHES	log per-batch progress (1/true)	false
DBT_VECTORIZE_DROP_SOURCE_IN_DBT	force dropping __vector_src in dbt phase (normally kept for embedder)	0
VECTOR_SEARCH_PROBES	pgvector IVFFLAT probes for search	10
VECTOR_SEARCH_COLUMNS	default result columns for search	doc_id,text,source,created_at

3. Run vectorization (dbt model + embedding upsert):

PGHOST=localhost PGPORT=5432 PGUSER=postgres PGDATABASE=postgres \
EMBED_PROVIDER=... EMBED_MODEL=... EMBED_DIMS=... \
dbt-vectorize build --select vector_knowledge_base

You can override runtime settings either via env vars or flags:

dbt-vectorize build \
  --select vector_knowledge_base_incremental \
  --embed-provider local \
  --embed-model sentence-transformers/all-MiniLM-L6-v2 \
  --embed-dims 384 \
  --embed-db-batch-size 500

Incremental variant (embed only new/changed rows):

PGHOST=localhost PGPORT=5432 PGUSER=postgres PGDATABASE=postgres \
EMBED_PROVIDER=... EMBED_MODEL=... EMBED_DIMS=... \
dbt-vectorize build --select vector_knowledge_base_incremental

This model uses embed_incremental=true and only sends rows to the embedder when:

• doc_id is new, or
• created_at (updated_at_column) is newer than source_updated_at, or
• text changed.

Large delta handling:

• pg_embedder processes source rows in database batches (default EMBED_DB_BATCH_SIZE=1000).
• Set EMBED_DB_BATCH_SIZE lower/higher to trade memory for throughput.
• pgvector macro creates supporting indexes (key/timestamp/vector) on target for production use.

Shortcut with env file:

cp .env.vectorize.example .env.vectorize
./bin/vectorize --select vector_knowledge_base

bin/vectorize auto-loads .env.vectorize if present. Use VECTORIZE_ENV_FILE=/path/to/file to load a different env file.

CLI with project env file (recommended):

# in your dbt project root
cat > .env.vectorize <<'EOF'
EMBED_PROVIDER=local
EMBED_MODEL=sentence-transformers/all-MiniLM-L6-v2
EMBED_LOCAL_MODEL_PATH=/path/to/ml_model
EMBED_DIMS=384

PGHOST=postgres-test.datascience.svc.cluster.local
PGPORT=5432
PGUSER=vectorize
PGPASSWORD=vectorize
PGDATABASE=vectorize
SCHEMA=public
EOF

set -a
source .env.vectorize
set +a

Now you can run without repeating provider/DB env vars:

dbt-vectorize build --select vector_knowledge_base --project-dir . --profiles-dir .
dbt-vectorize search --select vector_knowledge_base --query "oauth callback issues" --top-k 5 --include-distance --project-dir . --profiles-dir .

Search (semantic nearest-neighbor):

dbt-vectorize search \
  --select vector_knowledge_base \
  --query "oauth callback issues" \
  --top-k 5 \
  --format table \
  --include-distance

Production search recipe:

DBT=/opt/homebrew/bin/dbt \
EMBED_PROVIDER=local \
EMBED_MODEL=sentence-transformers/all-MiniLM-L6-v2 \
EMBED_LOCAL_MODEL_PATH=$PWD/ml_model \
EMBED_DIMS=384 \
VECTOR_SEARCH_PROBES=50 \
dbt-vectorize search \
  --select vector_knowledge_base_2000_varied \
  --query "oauth callback issues" \
  --top-k 5 \
  --include-distance

Search tuning notes:

• --top-k: how many nearest rows to return.
• VECTOR_SEARCH_PROBES: pgvector IVFFLAT probe count (10 default). Higher = better recall, slower query.
• If IVFFLAT returns no candidates, search falls back to an exact scan automatically.
• Use --format json for programmatic consumption.
• --columns doc_id,text,source,created_at controls returned fields (must include doc_id,text).

Inspect resolved model config:

dbt-vectorize inspect --select vector_knowledge_base

Embed-only rerun (no dbt run):

dbt-vectorize embed \
  --index-name knowledge_base_2000_varied \
  --schema public \
  --embed-db-batch-size 250 \
  --embed-max-batch 250 \
  --verbose

Use this when ...__vector_src already exists (e.g., after a prior --keep-source build).

Verbose batch logging (example: 2000 rows in chunks of 250):

dbt-vectorize build \
  --select vector_knowledge_base_2000 \
  --embed-db-batch-size 250 \
  --embed-max-batch 250 \
  --verbose

Expected embedder logs:

[pg_embedder] db batch 1 fetched 250 rows (limit=250, total_before=0)
...
[pg_embedder] db batch 8 fetched 250 rows (limit=250, total_before=1750)
embedded 2000 rows into public.knowledge_base_2000

Build safety/debug flags:

• --limit N embeds only the first N rows from __vector_src (debug only).
• --allow-partial is required with --limit to avoid accidental partial indexes.
• --keep-source keeps ...__vector_src after embedding for inspection (default drops it).

Expected CLI output (example):

[vectorize] running dbt model vector_knowledge_base (provider=local, model=sentence-transformers/all-MiniLM-L6-v2)
...
Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1
[vectorize] generating embeddings via Rust into public.knowledge_base
embedded 20 rows into public.knowledge_base
[vectorize] done.

Quick verification in Postgres:

SELECT count(*) AS rows FROM public.knowledge_base;

SELECT
  doc_id,
  (embedding::float4[])[1:8] AS first_8_dims,
  source,
  created_at
FROM public.knowledge_base
LIMIT 5;

Run dbt checks for incremental embeddings:

EMBED_DIMS=384 dbt test --profiles-dir . --project-dir . --select vector_knowledge_base_incremental

Optional Docker Postgres

Use this only if you want a disposable local pgvector instance:

docker-compose up -d postgres

If Docker/Colima is not running, this will fail with a daemon connection error.

Build pip package (dbt-vectorize)

Build from repo root (factorlens-style, bundles Rust binary in wheel):

./scripts/build_wheel_with_binary.sh

Artifacts will be written to dist/. Install locally:

python -m pip install dist/dbt_vectorize-*.whl

CLI entrypoint after install:

dbt-vectorize build --select vector_knowledge_base

CI release wheel build (macOS arm64 + Linux x86_64):

• workflow file: .github/workflows/release.yml
• trigger manually from Actions or push a v* tag
• outputs platform-specific wheels under workflow artifacts / GitHub release assets

Supported embedding dimensions (set EMBED_DIMS to match)

• OpenAI text-embedding-3-small: 1536 (can request smaller via API parameter)
• OpenAI text-embedding-3-large: 3072 (can request smaller)
• Bedrock Titan embed text v2: 1024 (or 512/256)
• Bedrock Titan embed text v1: 1024 (or 512/256)
• Bedrock Cohere Embed v4: 1536 (or 1024/512/256)
• Local MiniLM (all-MiniLM-L6-v2 ONNX): 384

Notes

• The Rust embedder is Python-free.
• Keep your Postgres vector column dimension aligned with EMBED_DIMS.
• IVFFLAT indexes warn on very small datasets; that’s expected. Rebuild after you have more rows.