REST Spec: Add unregister table endpoint#16400
Conversation
Co-Authored-By: Claude Code (Opus 4.7, 1M context) <noreply@anthropic.com>
nssalian
left a comment
nssalian
left a comment
There was a problem hiding this comment.
Left a comment, but I think the branch needs a rebase
| @@ -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' | |||
There was a problem hiding this comment.
I think this could include a$ref: '#/components/parameters/idempotency-key' too
| can be registered in another catalog. | ||
|
|
||
|
|
||
| On success, this returns the table's last metadata location and current |
There was a problem hiding this comment.
I am slightly worried about the ambiguity here of "last" and "current". Just want to make sure we are clearly stating that these should be pointing to identical representations of the table. The this returns the table's current metadata location and metadata.
There was a problem hiding this comment.
+1, Could we just use the word "corresponding" here to unambiguously bridge the two? "table's last metadata location and the corresponding table metadata"
There was a problem hiding this comment.
+1 on using corresponding.
| @@ -3792,6 +3592,22 @@ components: | |||
| type: boolean | |||
| default: false | |||
|
|
|||
| UnregisterTableResult: | |||
| description: | |||
| Last metadata location and current table metadata for the table that | |||
There was a problem hiding this comment.
Again slightly worried about "last" and "current"
6 participants
This adds an endpoint to
unregistera table from a REST catalog without deleting data or metadata files. Aregisterendpoint already exists to add a table to a REST catalog, since most migrations have been to REST from Hive or other catalogs. But anunregisterendpoint is needed to safely migrate from one REST catalog to another through the API.This uses an empty POST to
unregisterunder a table resource (/v1/{prefix}/namespaces/{namespace}/tables/{table}/unregister), rather than along side theregisterendpoint, which would require an unregister-specific request.The request and endpoint structure were co-authored by Claude Code (Opus 4.7).