Chris LuandDevin 8e44178dc6 s3vectors: cap PutVectors at 500 items and check data against the index dimension (#12200) ...

* s3vectors: cap PutVectors at 500 items and check data against the index dimension

A batch could carry any number of vectors and a vector of the wrong
dimensionality reached the engine: AWS caps a PutVectors call at 500 items
and requires each vector to match the index's declared dimension.

* s3vectors: cover the PutVectors batch and dimension checks

* s3vectors: reject query vectors that do not match the index dimension

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* s3vectors: cover the PutVectors batch size bounds

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* s3vectors: cover the catalog-backed PutVectors handler path

Run PutVectors through the real handlers over the in-memory catalog: a
matching vector reaches the engine, a mismatching one is rejected with
ValidationException before PutVectors is called, and a full
vectorsMaxPutBatch batch is accepted.

---------

Co-authored-by: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-10-29 11:14:30 -07:00

..

auth_test.go

vector: cover the identity object in s3vectors auth (#12162)

2026-10-28 01:47:12 -07:00

handlers_test.go

s3vectors: cap PutVectors at 500 items and check data against the index dimension (#12200)

2026-10-29 11:14:30 -07:00

handlers.go

s3vectors: cap PutVectors at 500 items and check data against the index dimension (#12200)

2026-10-29 11:14:30 -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