Skip to main content

match_query

velesdb_server

Function match_query 

Source 
pub async fn match_query(
    __arg0: Path<String>,
    __arg1: State<Arc<AppState>>,
    __arg2: Json<MatchQueryRequest>,
) -> Response
Expand description

Execute a MATCH query on a collection.

§Endpoint

POST /collections/{name}/match

§Example Request

{
  "query": "MATCH (a:Person)-[:KNOWS]->(b) WHERE similarity(a.vec, $v) > 0.8 RETURN a.name",
  "params": {
    "v": [0.1, 0.2, 0.3]
  }
}

§Errors

All failures are mapped through the canonical auto_core_error_response, so the JSON body carries the VELES-XXX code and the HTTP status is derived from the core error variant:

  • 404 NOT_FOUND (VELES-002) — collection not found
  • 400 BAD_REQUEST (VELES-010) — parse error, not a MATCH query, invalid threshold, or an unbound query parameter
  • other core variants map per [super::helpers::http_status_for_error]