kevinjqliu commented on issue #1404:
URL: 
https://github.com/apache/iceberg-python/issues/1404#issuecomment-3448913767

   Hi @srstrickland thanks for raising this. 
   
   Seems like this is an issue with the server side implementation of the 
iceberg rest catalog interface, and it looks like the glue team is aware based 
on https://github.com/apache/iceberg-python/issues/2511#issuecomment-3402084041
   
   > We must either wait for AWS to deploy a fix or for pyiceberg to support 
the native interface
   
   Do you know if a native s3tables implementation would resolve this issue? 
#1429 has the `commit_table` function implemented and we can test to see if it 
can unblock this particular issue. 
   
   > It was my understanding that the glue/rest interface was a stopgap and 
there was still a plan to support s3tables natively. Is that no longer the case?
   
   In my opinion, the rest interface is the preferred over specific 
implementations. This takes the maintenance burden away from pyiceberg. Client 
and server should speak the same [REST 
protocol](https://iceberg.apache.org/rest-catalog-spec/). The pyiceberg client 
wont need to worry about specific implementations. It can reuse the same logic 
for the glue rest catalog and every other rest catalog. 


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