CD
Cloudflare Developers•2y ago
zwily

Metadata filtering · Vectorize

I just started using Vectorize, and the query result shape is different than what's in the @cloudflare/workers-types@4.20240614.0: 
{
  "count": 1,
  "matches": [
    {
      "vectorId": "145",
      "score": 0.582596078,
      "vector": {
        "id": "145",
        "values": [],
        "metadata": {
          "content": "foo"
        }
      }
    }
  ]
}
{
  "count": 1,
  "matches": [
    {
      "vectorId": "145",
      "score": 0.582596078,
      "vector": {
        "id": "145",
        "values": [],
        "metadata": {
          "content": "foo"
        }
      }
    }
  ]
}
Note the new vector object in each result object. This also doesn't match what's in the docs: https://developers.cloudflare.com/vectorize/reference/metadata-filtering/ Did this change recently?
Cloudflare Docs
Metadata filtering · Vectorize
In addition to providing an input vector to your query, you can also filter by vector metadata associated with every vector. Query results only …
1 Reply
yevgen
yevgen•2y ago
@cfnathan when did we roll out this change? I believe it was in Q1. We should update our docs to reflect changes in API format.

Did you find this page helpful?