- Text Store — preconfigured vector storage with hybrid search, deduplication, and grouping. No schema or index setup required.
- Tables — low-level access to the vector database with full control over schema, indices, filters, and search operations.
Create a text store
Provide a name and the embedding dimension for your vectors.Add texts to a text store
Add texts with their pre-computed embedding vectors. Duplicate texts are automatically skipped. Thegroup field tags entries so you can delete or retrieve them as a set later.
Search a text store
Pass a text query and its embedding vector. The service runs a hybrid search combining full-text and vector similarity.Delete text from a text store
Remove specific entries by their exact text values.Delete texts by group from a text store
Remove all entries that belong to one or more groups.Delete a text store
Remove the store and all of its data.Advanced Usage: Tables
Tables give you direct access to the underlying vector database. You define the schema, choose which fields to index, insert structured rows, and compose search operations yourself.Schema fields
Each field in a table schema has aname, type, and optional properties.
| Type | Description | Index support |
|---|---|---|
string | Text data | FTS (full-text search) |
int | 32-bit integer | BTREE, BITMAP, LABEL_LIST |
float | 64-bit floating point | BTREE, BITMAP, LABEL_LIST |
datetime | Timestamp with optional timezone | BTREE |
vector | Fixed-dimension embedding | IVF_FLAT, IVF_PQ, IVF_HNSW_PQ, IVF_HNSW_SQ |
list | List of strings, ints, or floats | — |
nullable to false for required fields.
Add "index": "FTS" on a string field to enable full-text search at creation time.
Vector fields require a dimensions property that matches your embedding size.
Create a search table
Define a table with a schema that describes your records. The example below creates a support knowledge base with a text field indexed for full-text search and a vector field for semantic search.Insert rows
Insert records that match the table schema. You can send multiple rows in a single request.Search operations
Table search lets you compose multiple operations in a single request. Operations run in order — start with a primary search, then refine with filters, limits, or offsets. Primary operations initialize the result set:| Operation | Description |
|---|---|
vector_search | Find rows closest to a query vector. Supports cosine, l2, dot, and hamming distance types. |
fts | Full-text keyword search on one or more string fields. |
| Operation | Description |
|---|---|
filter | Apply a SQL-like expression. Set prefilter to true to filter before ranking. |
limit | Cap the number of returned rows. |
offset | Skip the first N rows for pagination. |
returnColumns to control which fields come back in the response.
Search the table
The example below combines a vector search with a pre-filter on thecategory field.