Apache Polaris
<https://www.google.com/url?q=https://polaris.apache.org/&sa=D&source=calendar&usd=2&usg=AOvVaw18ecah6mTe4LFpjyNIjRG4>currently
only functions as a catalog for Apache Iceberg
<https://www.google.com/url?q=https://iceberg.apache.org/&sa=D&source=calendar&usd=2&usg=AOvVaw3Z1f_NXxESBMc2N5hGuY5m>
tables through the Iceberg REST Catalog API. However, many users or engines
(i.e. Apache Spark
<https://www.google.com/url?q=https://spark.apache.org/&sa=D&source=calendar&usd=2&usg=AOvVaw1SdiAu9rfxH98y05lq5Zql>,
Trino
<https://www.google.com/url?q=https://trino.io/&sa=D&source=calendar&usd=2&usg=AOvVaw0skmaJMOxo6KWdP85nq2MV>,
Snowflake
<https://www.google.com/url?q=https://docs.snowflake.com/en/user-guide/intro-key-concepts&sa=D&source=calendar&usd=2&usg=AOvVaw0CaC3U2VgAiRAuF3tY63pa>
etc) also work with other table formats like Delta
<https://www.google.com/url?q=https://github.com/delta-io/delta&sa=D&source=calendar&usd=2&usg=AOvVaw2uDLRjz3zl3AE5ZRs4B8P1>.
In order for Polaris to provide better interoperability across different
engines, we should provide the capability for Polaris to manage non-Iceberg
tables, which we call *Generic Table* in Polaris.

Here, we propose a way to manage Generic tables in Polaris, as well as a
new Spark Catalog plugin for Spark to work with Polaris.

Here is a link to the proposal doc: Generic Table Support in Apache Polaris
<https://docs.google.com/document/d/1_R9jBIwoH3CV9G7gSoRJPQVEcOsROp4IEiGoeYeQE8A/edit?tab=t.0>
.

Please help review the proposal and provide your valuable feedback.

Best Regards,
Yun

Reply via email to