(iceberg) branch main updated: Spec: Clarify in REST spec that server implementations of commit endpoints must fail with 400 if any unknown updates or requirements are received (#10848)

[am...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

amoghj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg.git


The following commit(s) were added to refs/heads/main by this push:
     new 10fce2700e Spec: Clarify in REST spec that server implementations of commit endpoints must fail with 400 if any unknown updates or requirements are received (#10848)
10fce2700e is described below

commit 10fce2700e235c9a1f505fcbe14ba435b20283b9
Author: Amogh Jahagirdar <am...@apache.org>
AuthorDate: Fri Aug 16 17:25:34 2024 -0600

    Spec: Clarify in REST spec that server implementations of commit endpoints must fail with 400 if any unknown updates or requirements are received (#10848)
---
 open-api/rest-catalog-open-api.yaml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/open-api/rest-catalog-open-api.yaml b/open-api/rest-catalog-open-api.yaml
index 661af11efc..7f0619aff4 100644
--- a/open-api/rest-catalog-open-api.yaml
+++ b/open-api/rest-catalog-open-api.yaml
@@ -686,6 +686,8 @@ paths:
         Commits have two parts, requirements and updates. Requirements are assertions that will be validated
         before attempting to make and commit changes. For example, `assert-ref-snapshot-id` will check that a
         named ref's snapshot ID has a certain value.
+        Server implementations are required to fail with a 400 status code
+        if any unknown updates or requirements are received.
 
 
         Updates are changes to make to table metadata. For example, after asserting that the current main ref
@@ -986,7 +988,8 @@ paths:
           A commit for a single table consists of a table identifier with requirements and updates.
           Requirements are assertions that will be validated before attempting to make and commit changes.
           For example, `assert-ref-snapshot-id` will check that a named ref's snapshot ID has a certain value.
-
+          Server implementations are required to fail with a 400 status code
+          if any unknown updates or requirements are received.
 
           Updates are changes to make to table metadata. For example, after asserting that the current main ref
           is at the expected snapshot, a commit may add a new child snapshot and set the ref to the new