[ 
https://issues.apache.org/jira/browse/HIVE-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028725#comment-14028725
 ] 

Brock Noland edited comment on HIVE-7195 at 6/12/14 1:53 AM:
-------------------------------------------------------------

bq. API will need to be augmented to explicitly say what is needed/not needed.

Any changes to the HMS API should use the single request object argument model 
as opposed to the current method of multiple arguments to a method. This will 
allow us to easily iterate on these API's without breaking compatibility.


was (Author: brocknoland):
bq. API will need to be augmented to explicitly say what is needed/not needed.

Any changes to the HMS API should use the single request/response object model 
as opposed to the current method of multiple arguments to a method. This will 
allow us to easily iterate on these API's without breaking compatibility.

> Improve Metastore performance
> -----------------------------
>
>                 Key: HIVE-7195
>                 URL: https://issues.apache.org/jira/browse/HIVE-7195
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Brock Noland
>            Priority: Critical
>
> Even with direct SQL, which significantly improves MS performance, some 
> operations take a considerable amount of time, when there are many partitions 
> on table. Specifically I believe the issue:
> * When a client gets all partitions we do not send them an iterator, we 
> create a collection of all data and then pass the object over the network in 
> total
> * Operations which require looking up data on the NN can still be slow since 
> there is no cache of information and it's done in a serial fashion
> * Perhaps a tangent, but our client timeout is quite dumb. The client will 
> timeout and the server has no idea the client is gone. We should use 
> deadlines, i.e. pass the timeout to the server so it can calculate that the 
> client has expired.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to