[Vectorize] Clarify metadata filtering note

Author: netgusto

src/content/docs/vectorize/reference/metadata-filtering.mdx

@@ -7,14 +7,6 @@ sidebar:
 
 import { Render, PackageManagers } from "~/components";
 
-:::note[Enable metadata filtering]
-
-Vectorize requires metadata indexes to be specified before vectors are inserted to support metadata filtering. `string`, `number` and `boolean` metadata indexes are supported. Please refer to [Create metadata indexes](/vectorize/get-started/intro/#4-optional-create-metadata-indexes) for details.
-
-Vectorize supports [namespace](/vectorize/best-practices/insert-vectors/#namespaces) filtering by default.
-
-:::
-
 In addition to providing an input vector to your query, you can also filter by [vector metadata](/vectorize/best-practices/insert-vectors/#metadata) associated with every vector. Query results only include vectors that match `filter` criteria, meaning that `filter` is applied first, and `topK` results are taken from the filtered set.
 
 By using metadata filtering to limit the scope of a query, you can filter by specific customer IDs, tenant, product category or any other metadata you associate with your vectors.
@@ -29,6 +21,14 @@ For metadata indexes of type `string`, each vector indexes the first 64B of the
 
 See [Vectorize Limits](/vectorize/platform/limits/) for a complete list of limits.
 
+:::note[Enable metadata filtering]
+
+Vectors upserted before a metadata index was created won't have their metadata contained in that index. Upserting/re-upserting vectors after it was created will have them indexed as expected. Please refer to [Create metadata indexes](/vectorize/get-started/intro/#4-optional-create-metadata-indexes) for details.
+
+Vectorize supports [namespace](/vectorize/best-practices/insert-vectors/#namespaces) filtering by default.
+
+:::
+
 ## Supported operations
 
 Optional `filter` property on `query()` method specifies metadata filter: