rahulsmahadev commented on code in PR #17727:
URL: https://github.com/apache/iceberg/pull/17727#discussion_r4140164381


##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -2185,51 +2190,54 @@ components:
       name: User-Agent
       in: header
       description: >
-        Recommended header for a client to identify itself to the catalog. It
-        follows the standard HTTP `User-Agent` grammar (RFC 7231, Section
-        5.5.3): a whitespace-separated list of `product/version` tokens,
-        optionally followed by a parenthesized comment.
-
-
-        Tokens SHOULD be ordered from the outermost component to the innermost,
+        Header for a client to identify itself to the catalog. It follows the
+        standard HTTP `User-Agent` grammar (RFC 7231, Section 5.5.3): a
+        whitespace-separated list of `product/version` tokens, optionally
+        followed by a parenthesized comment.
+
+
+        Clients SHOULD send this header. When it is sent, the Iceberg client
+        library token MUST be present so that a server can always identify the
+        library and its version: use `iceberg-java`, `pyiceberg`,
+        `iceberg-rust`, or `iceberg-go`. A client not built on an Iceberg
+        library uses its own product token in that position. The remaining
+        tokens SHOULD be ordered from the outermost component to the innermost,
         so the most specific caller appears first: the engine or application,
-        then any integration or connector, then the Iceberg client library,
-        then the language runtime. The Iceberg client library token is the one
-        component every client can supply and SHOULD always be present.
-        Recommended library tokens are `iceberg-java`, `pyiceberg`,
-        `iceberg-rust`, and `iceberg-go`.
+        then any integration or connector, then the Iceberg library, then the
+        language runtime.

Review Comment:
   Done



-- 
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