rahil-c commented on code in PR #9695:
URL: https://github.com/apache/iceberg/pull/9695#discussion_r1623723419
##########
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:
> > does every server which supports planning also need to support
preplanning
>
> I think no, a server can decide to only implement one API. The server can
**require** the client to go through the preplan API by indicating a server
capability (e.g. preplanning), and in that case if the client still directly
hits the plan endpoint without a plan task, then a 421 Misdirected Request
should be thrown.
I agree with this. So to confirm we are saying that these two should be
separate capabilities, `preplanning` and `planning`, however only the `plan`
api is required to be implemented where as `preplan` is not required.
@jackye1995 @amogh-jahagirdar
--
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: issues-unsubscr...@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
