Chris Lu ac7b4f4cf6 s3vectors: bound ListVectorBuckets and ListIndexes maxResults (#12218) ...

* s3vectors: bound ListVectorBuckets and ListIndexes maxResults

Both pass maxResults to the catalog unbounded; AWS caps these list pages
at 100, the same way ListVectors is bounded and topK is bounded.

* s3vectors: raise ListVectorBuckets/ListIndexes maxResults cap to 500

AWS documents a valid range of 1-500 for both list APIs; the shared
limit of 100 rejected legitimate page sizes.

* s3vectors: reject explicit maxResults of zero on list calls

AWS requires maxResults >= 1, but a plain int field cannot tell an
omitted field from an explicit zero. Making MaxResults a pointer keeps
the catalog default for omitted fields while a supplied zero fails
validation.

* s3vectors: test max ListIndexes page against an existing bucket

2026-10-29 15:02:30 -07:00

..

auth_test.go

s3vectors: fix shared API behavior and test Go/Rust volume parity (#12216)

2026-10-29 13:35:05 -07:00

handlers_test.go

s3vectors: bound ListVectorBuckets and ListIndexes maxResults (#12218)

2026-10-29 15:02:30 -07:00

handlers.go

s3vectors: bound ListVectorBuckets and ListIndexes maxResults (#12218)

2026-10-29 15:02:30 -07:00

owner_check_test.go

s3vectors: keep bucket policies in vector form and evaluate them in the gateway (#12214)

2026-10-29 13:35:34 -07:00

server.go

s3vectors: fix shared API behavior and test Go/Rust volume parity (#12216)

2026-10-29 13:35:05 -07:00

types.go

s3vectors: bound ListVectorBuckets and ListIndexes maxResults (#12218)

2026-10-29 15:02:30 -07:00