Thejas M Nair commented on HIVE-18712:

Thanks for creating this. The API's can certainly use some cleanup.
These API's might be used in other projects as well, so we need to have some 
deprecation cycle for this.

There are many API's that do very similar things. I think lot of those would 
not have been needed if we had followed the pattern of using a single *Request 
object as argument and *Response argument as response. It would have been 
possible to evolve API by adding members to the Request/Response objects 
instead of exploding the number of functions. (HiveServer2 thrift API has seen 
better usage of this pattern).

I also see demand for HTTP based API's. This would allow the use of an HTTP 
gateway, specially in cloud environments. Supporting Thrift over HTTP is an 
option for that in the short term. Longer term, a REST API would be good to 
have. The webhcat DDL API's could be moved to metastore server, instead of 
keeping it in a separate server (we should also stop forking a "hcat cli" 
process to get the results!).

> 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