flyrain opened a new issue, #577: URL: https://github.com/apache/polaris/issues/577
### Is your feature request related to a problem? Please describe. _No response_ ### Describe the solution you'd like Polaris is designed to act as a **REST facade for S3 tables**, enabling both **read** and **write** operations by interacting with the S3 table API. Polaris registers an S3 table using its **metadata location**. A flag will be needed to label the new Iceberg table is a s3 table. Below is a summary of the proposed approach: ### **Read Path** - The **LoadTable** endpoint in Polaris will call the S3 table API `get_table_metadata_location` to fetch the `metadata.json` file. - Polaris will then **serialize** the content of the `metadata.json` into a **LoadTableResponse** to return to the client. ### **Write Path** When the table is updated, Polaris will: 1. Gather the changes and generate a new `metadata.json`. 2. Use the S3 table API [`update-table-metadata-location`](https://docs.aws.amazon.com/cli/latest/reference/s3tables/update-table-metadata-location.html) to commit the new metadata. ### **AuthZ/AuthN** We need to ensure that the AWS role used for creating the Polaris catalog has the read and write privileges of the s3 table. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- 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]
