rdblue commented on code in PR #15630:
URL: https://github.com/apache/iceberg/pull/15630#discussion_r3025035384


##########
format/spec.md:
##########
@@ -123,6 +138,35 @@ Tables do not require random-access writes. Once written, 
data and metadata file
 
 Tables do not require rename, except for tables that use atomic rename to 
implement the commit operation for new metadata files.
 
+### Paths in Metadata
+
+Path strings stored in Iceberg metadata files are classified as one of two 
types:
+
+* **Absolute path** -- A path string that includes a [URI 
scheme](https://datatracker.ietf.org/doc/html/rfc3986#section-3.1) (e.g., 
`s3://`, `gs://`, `hdfs://`, `file:///`). Absolute paths are used as-is without 
modification.

Review Comment:
   ```suggestion
   * **Absolute path** -- A path string that includes a [URI 
scheme](https://datatracker.ietf.org/doc/html/rfc3986#section-3.1) (e.g., 
`s3:`, `gs:`, `hdfs:`, `file:`). Absolute paths are used as-is without 
modification.
   ```
   
   We should remove the `//` from these to match [the URI 
RFC](https://datatracker.ietf.org/doc/html/rfc3986#section-3):
   > The authority component is preceded by a double slash ("//") and is 
terminated by the next slash ("/")
   
   The scheme is also the part before any non-scheme character, but I think it 
is fairly clear to include the `:`.
   
   Here's the grammar:
   ```
   URI         = scheme ":" hier-part [ "?" query ] [ "#" fragment ]
        hier-part   = "//" authority path-abempty
                    / path-absolute
                    / path-rootless
                    / path-empty
   ```



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