Vihang Karajgaonkar commented on HIVE-18712:

I think its a great idea to have v2 APIs. I think we should to make sure that 
APIs are extensible for the future. A lot of the our current APIs are not very 
extensible which caused everyone to add newer APIs which could have easily been 
implemented by extending the older ones. 

+1 to have request/response objects for the API instead of non-extensible input 
and output arguments.

I think one problem with the current APIs, is that there is no way to filter 
objects on the server side. For instance, it should be possible to get objects 
based on some filter criteria. Additionally, I think it would be good to have 
some way to fetch objects in batches rather than getting all the objects in one 
go. This adds a lot of memory pressure on HMS when clients requests huge number 
of objects.

I like the partition expression proxy API which enables clients to push down 
filters when querying partitions. We should have similar generic way to return 
only stuff which is needed by the clients.

Another interesting idea to consider is if we can have some kind of version 
handshake between client and server. This helps with cross-version 
compatibility. I am not sure how other systems handle these. But it would be 
good to take a look at that.

> 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