[
https://issues.apache.org/jira/browse/HIVE-28658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905019#comment-17905019
]
Shohei Okumiya commented on HIVE-28658:
---------------------------------------
I think I am on the same page as Butao. We need this ticket to make Hive as a
query engine(Do we have a better word to express the query engine part?) more
catalog-neutral. We need HIVE-28059(#5145) to make Hive Metastore more
applicable.
HIVE-28658(this ticket) enables HS2(Iceberg REST Catalog Client) -> Snowflake
Open Catalog(Iceberg REST Catalog API).
HIVE-28059(#5145) enables Snowflake[1](Iceberg REST Catalog Client) -> Hive
Metastore(Iceberg REST Catalog API).
HIVE-12679 is similar to the former one, and we have had some effort finding
the way. Let me share my analysis on the integration between HS2 and HMS, and
what I was about to propose.
[https://docs.google.com/document/d/1fFvB0DAXJvPYv27R8nLa3tOUT67-hY0owxBrDY-BxUA/edit?usp=sharing]
- [1] This should be a product that doesn't support HMS but support Iceberg
REST Catalog, but I don't know the example
> 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)
