Hi Andrew and everyone, Adding pagination to the Management API would be very helpful.
As to reusing the pagination parameter sepantics of the Iceberg REST spec... I'm not so sure. I do believe that servers should have ultimate control over page sizes. So any client-side "size" parameters should be suggestions or hints at most. As a continuation of that approach, the server should always be able to produce a partial response (with a next page token) even if the client did not provide any explicit pagination parameters. That said, given that existing clients may expect to get "full" results from the Management API when they do not use pagination parameters, I think it should be fine to enable that behaviour with a feature flag. WDYT? Thanks, Dmitri. On Fri, Oct 10, 2025 at 8:08 PM Andrew Guterman <[email protected]> wrote: > Hey folks, > > I wanted to gauge sentiment on adding pagination to non-IRC APIs, such as > the management APIs, as the number of management entities (catalogs, > principals, etc) can grow large and become un-listable all at once. > > I'm not sure if this has been discussed previously but I couldn't find a > thread nor PRs related to it. > > My proposal is to not reinvent the wheel and just re-use the spec and > implementation of the IRC APIs, where requests contain a "page-token" and > "page-size" param, and responses return a "next-page-token". > > Let me know what you think. > > Best, > Andrew >
