zhangbutao commented on code in PR #5870:
URL: https://github.com/apache/hive/pull/5870#discussion_r2158186754
##########
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:
It was a very good discussion. This discussion involved the further
development direction and positioning of HMS in the future.
First, I think we should write a detailed proposal and discuss it clearly in
the community email. Because I feel that many people are not clear about the
positioning of the HMS rest catalog, which may cause various misunderstandings.
Returning to the current issue, I basically agree with Denys' statement that
HMS(Rest) in the future will be similar to the Unity Catalog, capable of
serving as an Iceberg rest catalog server (its primary function), and also able
to register other catalogs (such as Hive tables from other HMS).
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
