RAG pipelines: slowly changing dimensions

By Michael Samuel Naeem · February 22, 2025 · 6 min read

RAG pipelines: slowly changing dimensions means you improve retrieval precision for slowly changing dimensions — with a named owner, a measurable signal, and a rollback a tired on-call can run. I reach for this when you are replacing a fragile legacy implementation; that is also when shortcuts like alerts on causes instead of user-visible symptoms start paging people.

This write-up is specific to rag-slowly-changing-dimensions in a rag context, using pgvector, OpenSearch, OpenTelemetry for the mechanics while keeping ownership human.

Fitting RAG pipelines: slowly changing dimensions into an existing system

RAG quality is mostly retrieval and chunking; the generator cannot invent missing evidence. For rag slowly changing dimensions, that means making failure visible early.

Put a metric on the user-visible effect of rag slowly changing dimensions before you optimize internals. If you are replacing a fragile legacy implementation, you need that graph on day one.

Document what 'success' and 'undo' mean in product language. Future reviewers will not share your context on rag slowly changing dimensions.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

Contracts and ownership boundaries

Teams usually discover RAG pipelines: slowly changing dimensions after a quiet failure — wrong data, slow pages, or a bill spike. Design for you are replacing a fragile legacy implementation.

Keep side effects at the edges and make every write idempotent. RAG pipelines: slowly changing dimensions without retry semantics is a future incident write-up.

Ship behind a flag, canary by cohort, and write the rollback in the PR description. RAG pipelines: slowly changing dimensions that needs a hero is not done.

Concretely, being able to improve retrieval precision for slowly changing dimensions forces explicit choices: source of truth, timeout budgets, and which errors users see versus operators.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

# RAG pipelines: slowly changing dimensions
from dataclasses import dataclass

@dataclass(frozen=True)
class RagSlowlyChangingRequest:
    tenant_id: str
    idempotency_key: str

async def run_rag_slowly_changing_dime(req, deps) -> None:
    if await deps.store.seen(req.idempotency_key):
        return
    with deps.tracer.start_as_current_span("rag-slowly-changing-dimensions"):
        await deps.client.execute(req, timeout=2.0)
    await deps.store.mark(req.idempotency_key)

State, storage, and retention

RAG quality is mostly retrieval and chunking; the generator cannot invent missing evidence. For rag slowly changing dimensions, that means making failure visible early.

With pgvector, OpenSearch, OpenTelemetry, the mechanics are straightforward; the hard part is invariants. The anti-pattern I still see is alerts on causes instead of user-visible symptoms.

Ship behind a flag, canary by cohort, and write the rollback in the PR description. RAG pipelines: slowly changing dimensions that needs a hero is not done.

My never-again list for rag slowly changing dimensions: alerts on causes instead of user-visible symptoms; shipping without a kill switch; and alerting only on infrastructure CPU.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

Security defaults that are non-negotiable

I treat RAG pipelines: slowly changing dimensions as an operations problem first. The goal is to improve retrieval precision for slowly changing dimensions, not to collect frameworks.

With pgvector, OpenSearch, OpenTelemetry, the mechanics are straightforward; the hard part is invariants. The anti-pattern I still see is alerts on causes instead of user-visible symptoms.

Acceptance check: an on-call engineer can explain system state for rag slowly changing dimensions from one dashboard and one runbook page.

Review prompts I use: what happens twice, what happens never, what happens partially? If RAG pipelines: slowly changing dimensions cannot answer, it is not production-ready.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

SLOs and dashboards

RAG quality is mostly retrieval and chunking; the generator cannot invent missing evidence. For rag slowly changing dimensions, that means making failure visible early.

With pgvector, OpenSearch, OpenTelemetry, the mechanics are straightforward; the hard part is invariants. The anti-pattern I still see is alerts on causes instead of user-visible symptoms.

Acceptance check: an on-call engineer can explain system state for rag slowly changing dimensions from one dashboard and one runbook page.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

Related reading:

• saga pattern distributed transactions
• designing for observability slos
• event driven outbox pattern

First-week validation plan

RAG quality is mostly retrieval and chunking; the generator cannot invent missing evidence. For rag slowly changing dimensions, that means making failure visible early.

Keep side effects at the edges and make every write idempotent. RAG pipelines: slowly changing dimensions without retry semantics is a future incident write-up.

Acceptance check: an on-call engineer can explain system state for rag slowly changing dimensions from one dashboard and one runbook page.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

Practical defaults for RAG pipelines: slowly changing dimensions

I treat RAG pipelines: slowly changing dimensions as an operations problem first. The goal is to improve retrieval precision for slowly changing dimensions, not to collect frameworks.

Put a metric on the user-visible effect of rag slowly changing dimensions before you optimize internals. If you are replacing a fragile legacy implementation, you need that graph on day one.

Document what 'success' and 'undo' mean in product language. Future reviewers will not share your context on rag slowly changing dimensions.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

Default deny, explicit timeouts, and one dashboard row for rag slowly changing dimensions. Expand only when the metric demands it.

Review questions before merging rag slowly changing dimensions work

Teams usually discover RAG pipelines: slowly changing dimensions after a quiet failure — wrong data, slow pages, or a bill spike. Design for you are replacing a fragile legacy implementation.

Keep side effects at the edges and make every write idempotent. RAG pipelines: slowly changing dimensions without retry semantics is a future incident write-up.

Acceptance check: an on-call engineer can explain system state for rag slowly changing dimensions from one dashboard and one runbook page.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

Default deny, explicit timeouts, and one dashboard row for rag slowly changing dimensions. Expand only when the metric demands it.

Field notes after thirty days of rag slowly changing dimensions

RAG quality is mostly retrieval and chunking; the generator cannot invent missing evidence. For rag slowly changing dimensions, that means making failure visible early.

Keep side effects at the edges and make every write idempotent. RAG pipelines: slowly changing dimensions without retry semantics is a future incident write-up.

Acceptance check: an on-call engineer can explain system state for rag slowly changing dimensions from one dashboard and one runbook page.

Slug-specific note (rag-slowly-changing-dimensions): prioritize dimensions behavior under load and verify with a fixture named rag-slowly-changing-dimensions-smoke.

After a month, delete unused flags and dual paths. rag-slowly-changing-dimensions accumulates temporary bridges faster than teams expect.

Resources

• Internal runbook seed: rag-slowly-changing-dimensions
• https://12factor.net/
• https://martinfowler.com/