Xuanwo commented on issue #450:
URL: https://github.com/apache/iceberg-rust/issues/450#issuecomment-2219661956

   > 1. How does connecting an Iceberg catalog with a specific S3 bucket work?
   
   Catalog will manage the bucket by their own. For example, to start a demo 
rest catalog, your can use:
   
   
https://github.com/apache/iceberg-rust/blob/3a947faaf33e8c9e31019581ec22b93f2b2437bc/crates/catalog/rest/testdata/rest_catalog/docker-compose.yaml#L21-L37
   
   > 2. Where does Pyiceberg fit into Iceberg-rust? Would it be possible to 
deploy Iceberg-rust on the server side, and interact with the rest catalog 
through Pyiceberg?
   
   Both pyiceberg and iceberg-rust implement the Iceberg specification. You can 
write an Iceberg table with iceberg-rust and then read it using pyiceberg.
   
   
   > 3. What are the write table options with an iceberg rust?
   
   iceberg-rust has not yet fully implemented support for DataFusion. 
Therefore, users will need to utilize the Rust APIs we provide to manipulate 
tables.
   
   > How does authentication and authorization work with the current 
Iceberg-rust?
   
   Iceberg-rust does not directly handle authentication or authorization. 
Typically, these functions are managed by catalog implementations. The 
community is moving to deprecate the token endpoint and adopt the OAuth2 
specification (not decided yet).
   
   > I am also not sure how this implementation compares with the open-sourced 
implementation released by Databricks.
   
   There should be no difference in iceberg-rust as long as it adheres to the 
iceberg-rest catalog specifications.
   
   > Where exactly does OpenDAL fit into the Iceberg-rust catalog?
   
   OpenDAL serves as the core file IO for iceberg-rust and does not directly 
interact with the catalog. However, it's possible to implement an iceberg 
catalog based on opendal.


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

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

Reply via email to