400 - invalid vector mode | OriginChainDB docs

What happened

The vector request names a search mode the endpoint does not accept. Use the exact spelling fast or high_recall.

Correct an unsupported vector search modeUse the accepted mode spelling; changing mode does not repair the underlying data.

Inspect the modeFind the rejected value in the search request.
Choose a supported valueUse fast or high_recall.
Repeat the corrected readCheck the returned IDs and scores.

Request that triggers it

Any mode value other than the two legal ones.

curl -X POST "https://$OC_HOST/v1/tenants/$OC_TENANT/vector/products/topk" \
  -H "Authorization: Bearer $OC_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query": [0.1, 0.2, 0.3], "k": 5, "mode": "warp_speed"}'

Read the response

{
  "error": "invalid_argument",
  "message": "mode 'warp_speed' is not supported; valid values are 'fast' and 'high_recall'",
  "retry": false
}

Fix the request

Read the mode field in the failing request.
Replace it with an accepted value.
Run the corrected request once.

Keep in mind: Set the mode explicitly; do not depend on a default inferred from older examples.

Common causes

Typo - high-recall with a hyphen, highrecall with no separator.
Carrying over a mode name from another vendor's API (exact, flat, approximate).
Configuration string read from an env var that wasn't validated at startup.
Casing - the enum is lower-case; Fast is rejected.

Continue

See error handling and retries, or return to error examples.

400 - invalid vector mode

What happenedCopy Anchor Link

Request that triggers itCopy Anchor Link

Read the responseCopy Anchor Link

Fix the requestCopy Anchor Link

Common causesCopy Anchor Link

ContinueCopy Anchor Link