From 07bf82c4a49de18566c43b4ac18ad53321bdaff9 Mon Sep 17 00:00:00 2001 From: Amogh Jahagirdar Date: Thu, 1 Aug 2024 16:25:10 -0700 Subject: [PATCH] Spec: Clarify in REST spec that server implementations of commit endpoints must fail with 400 if any unknown updates or requirements are received --- 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 661af11efc4b..7f0619aff4f9 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