DerGut opened a new issue, #2934: URL: https://github.com/apache/iceberg-rust/issues/2934
### Is your feature request related to a problem or challenge? By [the REST spec](https://datadoghq.atlassian.net/browse/DNAQ-5190), a REST catalog may return the `rest-page-size` property in a `/v1/config` response. The catalog client is then supposed to use it and provide it along with list requests via the `?pageSize` query parameter. Today, the Rust `RestCatalog` client doesn't look at the `rest-page-size` property and never sends a `pageSize` query parameter. It therefore depends on the catalog server to implement an implicit default page size. ### Describe the solution you'd like The spec already prescribes this fairly precisely. We'd use a precedence order similar to other properties: 1. catalog default from `/v1/config`: `{"defaults": {"rest-page-size": "1000"}}` (if provided) 2. overridden by client side config: `with_page_size(1000)` (else `None` or some client-side default[^1]) 3. overridden by catalog overrides from `v1/config`: `{"overrides": {"rest-page-size": "1000"}}` (if provided) [^1]: IIUC only `iceberg-go` currently sets a client-side default (20). Java and Python don't. ### Willingness to contribute I can contribute to this feature independently -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
