nornicdb-managed-embeddings

Managed Embeddings (Cypher API)

NornicDB can generate embeddings server-side and store them on nodes for you. From the consumer's point of view this is a Cypher feature: a WITH EMBEDDING clause on writes, and a db.index.vector.embed procedure for ad-hoc embedding.

Two storage slots, both readable

Every node has two embedding slots:

1. ChunkEmbeddings — managed by NornicDB. [][]float32 — one entry per chunk; ChunkEmbeddings[0] is the primary embedding. Built by the embedding worker or by WITH EMBEDDING. Internal metadata (model, dimensions, chunk_count, embedded_at) is stored separately so it does not pollute Properties.
2. NamedEmbeddings — client-managed. map[string][]float32, keyed by vector name (e.g. "default", "openai-small"). Set via db.create.setNodeVectorProperty or the Qdrant gRPC compatibility layer.

Vector index lookup order is NamedEmbeddings[indexProperty] → node.Properties[indexProperty] → ChunkEmbeddings. You usually want a vector index on a label whose nodes have managed embeddings, in which case nothing extra is needed.

Enabling managed embeddings

export NORNICDB_EMBEDDING_ENABLED=true
export NORNICDB_EMBEDDING_PROVIDER=ollama          # ollama | openai | orca | voyage | local
export NORNICDB_EMBEDDING_MODEL=mxbai-embed-large
export NORNICDB_EMBEDDING_API_URL=http://localhost:11434
export NORNICDB_EMBEDDING_DIMENSIONS=1024

YAML form:

embedding:
  enabled: true
  provider: ollama          # ollama | openai | orca | voyage | local
  model: mxbai-embed-large
  url: http://localhost:11434
  dimensions: 1024

The OpenAI, Orca, and Voyage providers read embedding.api_key (or NORNICDB_EMBEDDING_API_KEY). The local provider resolves the model file inside NORNICDB_MODELS_DIR.

Defaults shipped with NornicDB: provider=local, model=bge-m3, dimensions=1024.

Per-database configuration

For a named database, use canonical keys in the YAML databases: map or PUT /admin/databases/{name}/config: db.nornic.embedding.provider, db.nornic.embedding.model, db.nornic.embedding.api.url, db.nornic.embedding.api.key, db.nornic.embedding.mode, and db.nornic.embedding.dimensions. Their NORNICDB_* forms remain supported global environment alternatives and alternate input names; canonical keys win collisions.