Hi Prashant It makes sense to me. I guess we are using Catalog properties to indicate what the REST server supports to the client, right ? I will take a look at the PR, but I like the idea.
Regards JB On Sat, Dec 20, 2025 at 12:53 AM Prashant Singh <[email protected]> wrote: > Hey All, > > I wanted to bring up the discussion of introducing a concept of rest scan > planning mode which would help the server to instruct the client on how to > plan the table via loadTableResponse or config at table level override. > There are three possible values which one could think of : > 1. *None* : i.e plan it on the client side, this may be the table is too > small and the additional rest request would add more overhead than benefit. > 2. *Optional* : client can choose to plan it either locally or can > trigger server side planning. > 3. *Required* : client MUST do server side planning, the server could > suggest this if it has better indexed the iceberg metadata or client is > running on low resources or the table is protected. Server MAY choose > whatever way required to enforce the client cant bypass this for example > let's say don't vend cred as part of loadTable and only mint it part of > planning completion this would mean if the client doesn't call plan table . > > I proactively have created a pull request [1], would love to know all your > feedback either here or in the PR directly ! > > Wish you all a very happy Holidays, it has been great working with you > all. > > [1] https://github.com/apache/iceberg/pull/14867 > > Best, > Prashant Singh >
