Alexander Kolbasov commented on HIVE-18712:

A few things to consider:
 # What parts of the current API work really well
 # What parts are obsolete, do not work or work poorly

There are several other considerations:
 # Transport/Encoding:
 ** Thrift
 ** HTTP
 ** gRPC
 ** Something else?
 # Security
 ** Kerberos
 ** SSL
 ** Something else?
 # Compatibility
 # API evolution

It is also worth establishing higher-level design principles. I would argue 
that the following are useful:
 * API should be able to deal efficiently with very large amounts of objects. 
 * It should have clear failure model
 * It should not be tailored to any specific implementation language and should 
work reasonably well with at least 3 different ones
 * It should support metadata needs of existing known consumers


Please treat items above as a starting point of discussion - I am sure there 
will be lots and lots of various opinions on the subject.

> 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
>            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

Reply via email to