singhpk234 commented on code in PR #16394:
URL: https://github.com/apache/iceberg/pull/16394#discussion_r3329147404


##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -2019,6 +2058,50 @@ components:
       explode: false
       example: "vended-credentials,remote-signing"
 
+    client-capabilities:
+      name: X-Iceberg-Client-Capabilities
+      in: header
+      description: >
+        This header is a forward-compatibility hint, not a security mechanism.
+        Clients can trivially spoof its value; servers MUST NOT base trust or
+        authorization decisions on it.
+
+
+        Optional signal from the client declaring the set of capabilities that
+        the client SDK supports, as a comma-separated list. This header is
+        sent on every request. The server may use this information to tailor
+        its responses.
+
+
+        Defined capability values:
+
+        - `vended-credentials`: The client supports receiving and using
+          storage credentials vended by the catalog server.
+
+        - `remote-signing`: The client supports delegating request signing
+          to a remote signing service provided by the catalog server.
+
+        - `scan-planning`: The client supports server-side scan planning.

Review Comment:
   we discussed a bit about it 05/25, ReadRestrictions sync, please have a pass 
and let us know what you think in context of that, while versioning would be 
ideal, but for now considering where we are how we have been maintaining spec 
(in a backward compatible way) we can park that discussion, specially for read 
restrictions since we just need a signal that, hey i understand what 
"ReadRestrictions are" and not "I understand everything within the read 
restrictions"



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to