[
https://issues.apache.org/jira/browse/HIVE-28658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904816#comment-17904816
]
Denys Kuzmenko commented on HIVE-28658:
---------------------------------------
HS2 only supports HMS as a meta-provider. With the iceberg table format
becoming mainstream and ask for open standard API to interact with the catalog
we see a number of REST catalog solutions appearing on the market following
modern architecture and design. We'd like to add support for those in HS2 as
well and remove tight coupling with the HMS.
There is a work in progress planning to expose metadata in HMS via REST as well
(https://github.com/apache/hive/pull/5145). It might conflict with us since
they added a new abstraction just for iceberg meta-provider
* HiveActor (aka MetadataProvider),
* HiveCatalog (aka HiveCatalogActor)
> Iceberg REST Catalog Support
> -----------------------------
>
> Key: HIVE-28658
> URL: https://issues.apache.org/jira/browse/HIVE-28658
> Project: Hive
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
> Components: Iceberg integration
> Reporter: Denys Kuzmenko
> Assignee: Zoltán Rátkai
> Priority: Major
>
> Allow Hive to communicate directly with an Iceberg catalog service using the
> Iceberg REST Catalog protocol. This protocol is the standard and recommended
> way to interact with Iceberg metadata and tables.
> interface MetadataProvider
> * HiveCatalog
> * RestCatalog
> Ref:
> https://www.tabular.io/apache-iceberg-cookbook/getting-started-trino-configuration/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
