rambleraptor commented on code in PR #16400:
URL: https://github.com/apache/iceberg/pull/16400#discussion_r3262496453


##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -1217,29 +1181,31 @@ paths:
         5XX:
           $ref: '#/components/responses/ServerErrorResponse'
 
-  /v1/{prefix}/namespaces/{namespace}/tables/{table}/credentials:
+  /v1/{prefix}/namespaces/{namespace}/tables/{table}/unregister:
     parameters:
       - $ref: '#/components/parameters/prefix'
       - $ref: '#/components/parameters/namespace'
       - $ref: '#/components/parameters/table'
 
-    get:
+    post:
       tags:
         - Catalog API
-      summary: Load vended credentials for a table from the catalog
-      operationId: loadCredentials
-      parameters:
-        - name: planId
-          in: query
-          required: false
-          schema:
-            type: string
-          description: The plan ID that has been used for server-side scan 
planning
-        - $ref: '#/components/parameters/referenced-by'
-      description: Load vended credentials for a table from the catalog.
+      summary: Unregister a table without removing its data or metadata files
+      description:
+        Unregister a table from the catalog. This is the opposite of
+        `registerTable`. The table no longer exists in the catalog, but the
+        underlying data and metadata files are left in place so that the table
+        can be registered in another catalog.
+
+
+        On success, this returns the table's last metadata location and current

Review Comment:
   +1 on using `corresponding`. 



-- 
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]

Reply via email to