Hi.
The REST spec currently defines six write operations that return a 409
Conflict when an identifier already exists. However, the descriptions
of what constitutes a conflict are inconsistent:
- Enforcing cross-type uniqueness (table or view):
- renameTable, renameView, registerView say: *"already exists as a
table or view"*
- Only enforcing within the same type (table or view only):
- createTable, registerTable, createView say: *"table already exists"*
/ *"view already exists"*
I'd like to propose a vote on a small clarification in the REST spec to
apply the same wording of "*The identifier already* *exists as a table or
view*" across all 6 endpoints.
https://github.com/apache/iceberg/pull/15691/changes
Thanks,
Steven
