Skip to content

REST spec: Add Optional UUID for Namespaces to OpenAPI spec#15317

Open
talatuyarer wants to merge 2 commits intoapache:mainfrom
talatuyarer:rest-namespace-uuid
Open

REST spec: Add Optional UUID for Namespaces to OpenAPI spec#15317
talatuyarer wants to merge 2 commits intoapache:mainfrom
talatuyarer:rest-namespace-uuid

Conversation

@talatuyarer
Copy link
Contributor

This PR adds an optional namespace-uuid to REST API namespace responses. This UUID uniquely identifies a namespace, allowing name reuse, and supports catalog synchronization. We discussed at last Catalog Sync.


class CreateNamespaceResponse(BaseModel):
namespace: Namespace
namespace_uuid: str | None = Field(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better to put this under the Namespace itself as an optional field, similar to how it's done for TableMetadata/ViewMetadata. We will then most likely need a separate NamespaceParser that reads/writes that optional uuid. Right now we only have a NamespaceSerializer and NamespaceDeserializer which serDe the levels of the namespace directly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants