[
https://issues.apache.org/jira/browse/HIVE-28998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17984988#comment-17984988
]
Shohei Okumiya commented on HIVE-28998:
---------------------------------------
Just a note. I attended [a local Iceberg
event|https://iceberg.connpass.com/event/354741/] and heard the real-world use
cases of Cloudera's REST Catalog and self-hosted REST Catalog over the JDBC
Catalog. The latter speaker said they didn't choose the Hive Catalog because
setting up Kerberos sounded tough(yes, in my experience!). I asked him what his
preferred choice is. The answer was OAuth 2. It might be the potential target
with 4.2.0.
> Support Iceberg REST Catalog without authentication
> ---------------------------------------------------
>
> Key: HIVE-28998
> URL: https://issues.apache.org/jira/browse/HIVE-28998
> Project: Hive
> Issue Type: Improvement
> Components: Iceberg integration, Standalone Metastore
> Reporter: Shohei Okumiya
> Assignee: Shohei Okumiya
> Priority: Major
> Labels: hive-4.1.0-must
>
> The current Iceberg REST API supports only the SIMPLE and JWT-based
> authentications via `metastore.iceberg.catalog.servlet.auth`. However, as
> Iceberg REST Catalog is evolving independently of the Hadoop ecosystem,
> most(or even all) query engines don't support our choices. For example,
> [Trino supports only NONE or
> OAUTH2|https://trino.io/docs/current/object-storage/metastores.html#iceberg-rest-catalog].
> Although it is controversial what should be supported, it would be helpful
> to provide the non-auth mode for testing purposes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
