Namespace Qavren.Edge.VectorData

Classes

EdgeDynamicVectorStoreCollection

The trim/AOT-safe path, and a first-class one: the conformance suite runs against it too, and the trim-smoke job publishes it.

Its constructor carries no trim annotations, because it chains to the CollectionModel-taking base constructor rather than the reflecting one, and builds its model with CollectionModelBuilder.BuildDynamic, which reflects over nothing. (MEVD's reflection-based Build throws for Dictionary<TKey, TValue> by design.)

EdgeHybridSearchOptions<TRecord>

Per-query RRF tuning. A caller passing the plain MEVD HybridSearchOptions<TRecord> gets the store defaults and never sees this type.

EdgeVectorData

Constants shared by this package and the apps that wire it up.

EdgeVectorDataBuilderExtensions

Registers the vector store, its collections and their schema on the Qavren.Edge builder.

EdgeVectorModelException

Raised while building the collection model or validating the schema - always before any SQL runs.

EdgeVectorSchema

The DDL and the queries as plain strings, so a consumer can read, log or hand-execute exactly what the provider runs - the same visible-SQL contract as sub-project 1's helpers.

Nothing here opens a connection or executes anything. Every statement is emitted with \n line endings so the text is identical on every platform.

EdgeVectorStore

A Microsoft.Extensions.VectorData store over one sub-project 1 IEdgeDatabase. It never constructs a connection of its own, which is what lets it ride on an encrypted, pooled, pragma-configured database that a connection-string-based connector structurally cannot reach.

EdgeVectorStoreCollectionOptions

Per-collection overrides. Every null member falls back to the store-level default.

EdgeVectorStoreCollection<TKey, TRecord>

One collection: a data table, a vec0 sidecar, an optional FTS5 sidecar, and the triggers that keep the three in step. Every statement it runs is text EdgeVectorSchema emits, so a consumer can read, log or hand-execute it.

EdgeVectorStoreException

Derives from MEVD's VectorStoreException, not from EdgeException - the one deliberate break in the suite's hierarchy. The MEVD conformance suite asserts the MEVD type, and Semantic Kernel, Agent Framework and generic retry middleware all catch it; an Edge-only hierarchy would be invisible to every one of them. It still carries the EdgeErrorCode and sets the docs HelpLink explicitly, so Qavren's error contract holds on both sides of the line.

Note .NET MEVD 10.x has no VectorStoreOperationException; that type exists only in Semantic Kernel's Python SDK.

EdgeVectorStoreOperations

The fixed vocabulary MEVD's VectorStoreException.OperationName is drawn from. It matches the OpenTelemetry operation names upstream MEVD providers emit, so a trace reads the same either side of a migration.

EdgeVectorStoreOptions

Store-wide defaults. Every value here decides what SQL is emitted or how results are ordered.

RrfDefaults

The four numbers that compose the fused hybrid score. Getting one of them wrong produces a working query with wrong results, which is why each is transcribed and asserted.

Enums

KeywordCombinator

How the keywords of a hybrid search are combined into one FTS5 MATCH expression.