amogh-jahagirdar commented on code in PR #9695:
URL: https://github.com/apache/iceberg/pull/9695#discussion_r1545072167
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -537,6 +537,113 @@ paths:
5XX:
$ref: '#/components/responses/ServerErrorResponse'
+ /v1/{prefix}/namespaces/{namespace}/tables/{table}/preplan:
Review Comment:
More fundamental question: Since we're going down a route of adding a REST
catalog defining which capabilities are supported, does every server which
supports planning also need to support preplanning? Or are these different
capabilities? @nastra @rdblue
IMO I think these should be separate capabilities. Pre-planning seems like
it would require a lot more state to maintain on the server and it wouldn't
make sense to me to lump the 2 capabilities because then the barrier for any
given REST catalog implementation to technically support planning is
significantly higher, even though it would be valuable for users to be able to
just leverage the normal plan API.
--
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]
