Skip to main content
Vector is configured through CLI arguments and a YAML configuration file. The CLI arguments control server startup and mode, while the YAML file defines storage, vector properties, indexing parameters, and metadata schema.

CLI Arguments

Pass these flags when starting the opendata-vector binary. The binary has two subcommands: vector (read-write) and reader (read-only).

Configuration File

The configuration file is YAML. The generic placeholders used in this reference are:
  • <string>: a regular string
  • <int>: an integer value
  • <float>: a floating-point value
  • <bool>: true or false
A value enclosed in [ ] is optional. The default value is shown after | default =.

Read-Write Configuration

Read-Only Configuration

The reader configuration is a subset — it omits all write-specific fields (flush interval, split/merge thresholds, rebalancing, chunk target).

<storage_config>

Storage is tagged by type.
Stores data in memory only. Data is lost on restart. Useful for testing and development. No additional fields are required.

<object_store_config>

The object store is tagged by type.

<block_cache_config>

The block cache reduces object store reads by caching hot SST blocks in memory and on local disk. Tagged by type.

<metadata_field_spec>

Defines the schema for metadata attributes attached to vectors. When a schema is defined, writes with unknown attribute names or type mismatches will be rejected.
Schema evolution rules:
  • New fields can be added
  • Indexing can be enabled on existing fields
  • Fields cannot be removed, and types cannot be changed

Distance Metrics

Examples

vector.yaml