deniskuzZ commented on code in PR #5870:
URL: https://github.com/apache/hive/pull/5870#discussion_r2156625705
##########
standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java:
##########
@@ -1867,7 +1867,7 @@ public enum ConfVars {
" positive value will be used as-is."
),
ICEBERG_CATALOG_SERVLET_AUTH("metastore.iceberg.catalog.servlet.auth",
- "hive.metastore.iceberg.catalog.servlet.auth", "jwt", new
StringSetValidator("simple", "jwt"),
+ "hive.metastore.iceberg.catalog.servlet.auth", "jwt", new
StringSetValidator("none", "simple", "jwt"),
Review Comment:
hi @okumin,
The idea was to expose the metadata management functionality via REST in
HMS.
Currently we are focused only on exposing iceberg tables, however, we could
extend it with the support of Hive managed format like ACID.
Another thing is federation. Register multiple catalog connectors in HMS
(keep connection details with credentials in HMS DB) and expose it via same
Unified/Iceberg Rest API.
UnityCatalog already supports a Managed catalog and ability to integrate
with the Foreign catalogs like Glue, HMS, Iceberg Rest Catalogs.
| Service | AuthN supported by clients | users |
|-|-|-|
| HMS (HTTP over Thrift) | NONE(probably, like a SIMPLE), JWT | Hive, etc. |
| HMS (REST) | NONE, JWT, OAuth 2.0 | HMS clients |
The HMS RestCatalog would handle proxying metadata requests to either the
HMSHandler or one of the registered external catalogs, using the stored
connection details and credentials.
@okumin, does it make sence?
As far as I know, the Properties API isn't used by anyone. That was one of
my concerns, given the lack of a clear vision or usage patterns. I felt like
it's yet another key-value store bicycle without a defined purpose.
##########
standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java:
##########
@@ -1867,7 +1867,7 @@ public enum ConfVars {
" positive value will be used as-is."
),
ICEBERG_CATALOG_SERVLET_AUTH("metastore.iceberg.catalog.servlet.auth",
- "hive.metastore.iceberg.catalog.servlet.auth", "jwt", new
StringSetValidator("simple", "jwt"),
+ "hive.metastore.iceberg.catalog.servlet.auth", "jwt", new
StringSetValidator("none", "simple", "jwt"),
Review Comment:
hi @okumin,
The idea was to expose the metadata management functionality via REST in
HMS.
Currently we are focused only on exposing iceberg tables, however, we could
extend it with the support of Hive managed format like ACID.
Another thing is federation. Register multiple catalog connectors in HMS
(keep connection details with credentials in HMS DB) and expose it via same
Unified/Iceberg Rest API.
UnityCatalog already supports a Managed catalog and ability to integrate
with the Foreign catalogs like Glue, HMS, Iceberg Rest Catalogs.
| Service | AuthN supported by clients | users |
|-|-|-|
| HMS (HTTP over Thrift) | NONE(probably, like a SIMPLE), JWT | Hive, etc. |
| HMS (REST) | NONE, JWT, OAuth 2.0 | HMS clients |
The HMS RestCatalog would handle proxying metadata requests to either the
HMSHandler or one of the registered external catalogs, using the stored
connection details and credentials.
@okumin, does it make sense?
As far as I know, the Properties API isn't used by anyone. That was one of
my concerns, given the lack of a clear vision or usage patterns. I felt like
it's yet another key-value store bicycle without a defined purpose.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org
For additional commands, e-mail: gitbox-h...@hive.apache.org
