Skip to content

REST: Remove deprecated allowEmptyValue from REST spec#14364

Merged
huaxingao merged 2 commits into
apache:mainfrom
ebyhr:ebi/rest-allow-empty-value
Oct 22, 2025
Merged

REST: Remove deprecated allowEmptyValue from REST spec#14364
huaxingao merged 2 commits into
apache:mainfrom
ebyhr:ebi/rest-allow-empty-value

Conversation

@ebyhr

@ebyhr ebyhr commented Oct 18, 2025

Copy link
Copy Markdown
Member

Fixes #13444

If not provided or empty, all top-level namespaces should be listed.
If parent is a multipart namespace, the parts must be separated by the unit separator (`0x1F`) byte.
required: false
allowEmptyValue: true

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we remove or empty in L263? Also should we explicitly state that For backward compatibility, empty string is treated as absent for now?

@huaxingao

Copy link
Copy Markdown
Contributor

cc @elphastori @nastra

@huaxingao huaxingao merged commit cd097eb into apache:main Oct 22, 2025
10 checks passed
@huaxingao

Copy link
Copy Markdown
Contributor

Thanks @ebyhr for the PR! Thanks @elphastori for the review!

thomaschow pushed a commit to thomaschow/iceberg that referenced this pull request Jan 19, 2026
* REST: Remove deprecated allowEmptyValue from REST spec

* fixup! REST: Remove deprecated allowEmptyValue from REST spec
talatuyarer pushed a commit to talatuyarer/iceberg that referenced this pull request Apr 1, 2026
* REST: Remove deprecated allowEmptyValue from REST spec

* fixup! REST: Remove deprecated allowEmptyValue from REST spec
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.

Remove allowEmptyValue from REST Catalog OpenAPI Spec

3 participants