ajantha-bhat commented on code in PR #14869:
URL: https://github.com/apache/iceberg/pull/14869#discussion_r2696554270
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -1835,6 +1832,60 @@ paths:
5XX:
$ref: '#/components/responses/ServerErrorResponse'
+ /v1/{prefix}/namespaces/{namespace}/register-view:
+ parameters:
+ - $ref: '#/components/parameters/prefix'
+ - $ref: '#/components/parameters/namespace'
+
+ post:
+ tags:
+ - Catalog API
+ summary: Register a view in the catalog
+ parameters:
+ - $ref: '#/components/parameters/idempotency-key'
+ description:
+ Register a view in the given namespace using given metadata file
location.
+
+ operationId: registerView
+ requestBody:
+ required: true
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/RegisterViewRequest'
+ responses:
+ 200:
+ $ref: '#/components/responses/LoadViewResponse'
+ 400:
+ $ref: '#/components/responses/BadRequestErrorResponse'
+ 401:
+ $ref: '#/components/responses/UnauthorizedResponse'
+ 403:
+ $ref: '#/components/responses/ForbiddenResponse'
+ 404:
+ description: Not Found - The namespace specified does not exist
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/IcebergErrorResponse'
+ examples:
+ NamespaceNotFound:
+ $ref: '#/components/examples/NoSuchNamespaceError'
+ 409:
+ description: Conflict - The identifier already exists as a table or
view
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/IcebergErrorResponse'
+ examples:
+ ViewAlreadyExists:
+ $ref: '#/components/examples/ViewAlreadyExistsError'
Review Comment:
I saw this too before. And my thought is similar to Kevin. This is just an
example. So, no need to add `TableAlreadyExists` as the existing example for
`CreateView` doesn't mention about `TableAlreadyExists`.
I can update the examples for both createView and registerView to include
`TableAlreadyExists` if you want.
--
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]
