[
https://issues.apache.org/jira/browse/HIVE-29038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985811#comment-17985811
]
Shohei Okumiya commented on HIVE-29038:
---------------------------------------
So, let's conclude: We will start with the generic one. I started feeling that
we can add `metastore.iceberg.catalog.servlet.auth` later if needed, and make
the specialized one win.
> Conclude if we should consolidate authentication methods of REST
> ----------------------------------------------------------------
>
> Key: HIVE-29038
> URL: https://issues.apache.org/jira/browse/HIVE-29038
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
> Reporter: Shohei Okumiya
> Priority: Major
>
> We're developing the minimal viable product of Iceberg REST API on Hive
> Metastore. As part of this effort, we discussed the possibility of having a
> unified authentication property for all REST use cases.
> [https://github.com/apache/hive/pull/5870]
>
> In short, we are providing `metastore.iceberg.catalog.servlet.auth` to allow
> users to configure their preferred authentication method for Iceberg REST
> Catalog. There is an opinion that this property should be more generic, e.g.,
> `metastore.catalog.servlet.auth`, so that they can configure the
> authentication methods of all REST endpoints with a single property. The "all
> REST endpoints" mostly means the future proposal to provide a new unified
> metastore APIs such as Unity Catalog.
>
> Definition of Done. We want to conclude how to expose the authentication
> method for Iceberg REST API by the 4.1.0 release. If the conclusion is the
> consolidation, we will rename `metastore.iceberg.catalog.servlet.auth` into
> the new name. If the conclusion is separation, we will close this ticket
> without any changes. If we can not conclude, we will probably offer the
> Iceberg REST API as experimental in 4.1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
