Chris Lu afb8472c5e s3vectors: cover non-filterable key round-trip and nested filter rejection (#12160) ...

* s3vectors: cover non-filterable key round-trip and nested filter rejection

The catalog writes the key list as a JSON string while older records
may still carry the array form; indexFromRecord must decode both. The
rejection path extracts field names through nested $and/$or filters, so
a blocked key deep in the tree still fails the query.

* s3vectors: factor the non-filterable rejection into a testable gate

Pull the blocked-key check out of handleQueryVectors into
nonFilterableField so the rejection itself is covered without standing
up the catalog stack; the handler now 400s on whatever the gate names.

* s3vectors: report the non-filterable match separately from the key

An empty metadata key in nonFilterableMetadataKeys collided with the
"no match" sentinel, so a filter on that key skipped rejection. Return
a match flag and cover the empty-key case in the test.

2026-10-28 01:41:37 -07:00

..

handlers_test.go

s3vectors: cover non-filterable key round-trip and nested filter rejection (#12160)

2026-10-28 01:41:37 -07:00

handlers.go

s3vectors: cover non-filterable key round-trip and nested filter rejection (#12160)

2026-10-28 01:41:37 -07:00

server.go

vector: carry the full identity through s3vectors auth (#12152)

2026-10-28 00:33:52 -07:00

types.go

vector: address remaining s3vectors review findings (#12115)

2026-10-26 20:49:44 -07:00