[I] The identity partition path of timestamp type is inconsistent with java api [iceberg-python]

[via GitHub]

sharkdtu opened a new issue, #1735:
URL: https://github.com/apache/iceberg-python/issues/1735

   ### Feature Request / Improvement
   
   The human string of timestamp value is inconsistent with java api, which 
cause different partition paths.
   
   For example, let's say i have a table with following representation:
   ```
   table {
     1: hour: optional timestamptz
     2: id: optional long
     3: name: optional string
   },
   partition by: [hour],
   ...
   ```
   
   the writting data path of pyiceberg is:
   ```
   /path/to/namespace/table/data/hour=2025-02-27T00%3A00%3A00%2B00%3A00
   ```
   
   however, the writting data path of spark is:
   ```
   /path/to/namespace/table/data/hour=2025-02-27T00%3A00Z
   ```
   


-- 
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: issues-unsubscr...@iceberg.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org