[
https://issues.apache.org/jira/browse/HIVE-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443383#comment-16443383
]
Alexander Kolbasov commented on HIVE-18712:
-------------------------------------------
A few thoughts about the nature of the newish APIs.
* It would be difficult to convert a lot of existing apps to new APIs so we
need to preserve compatibility with existing HMS APIs.
* We would like to separate pure metadata operations from the rest of the work
done by HMS. This means that we may want to define "metadata API" and let HMS
use it.
* Currently this most closely matches ObjectStore layer. Note that ObjectStore
doesn't use Kerberos to talk to the underlying DB so we can define gRPC
non-kerberos API that talks to metadata service.
What would be a good way for us to start working on this and share the work?
Should we work in a branch off branch-3 or set up another git repo or use some
other tools?
Any suggestions?
> Design HMS Api v2
> -----------------
>
> Key: HIVE-18712
> URL: https://issues.apache.org/jira/browse/HIVE-18712
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Affects Versions: 3.0.0
> Reporter: Alexander Kolbasov
> Assignee: Alexander Kolbasov
> Priority: Major
>
> This is an umbrella Jira covering the design of Hive Metastore API v2.
> It is supposed to be a placeholder for discussion and design documents.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
