[
https://issues.apache.org/jira/browse/HIVE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996009#comment-12996009
]
Paul Yang commented on HIVE-1788:
---------------------------------
Talked with Ashish offline about this - a batch retrieval method for tables is
definitely required as the RTT would be excessive with 100's of tables. Another
approach that may work is to have an API that accepts a list of table names as
an input. Then, that could be used in conjunction with a method that returns
matching table names to deal with the inconsistent offset issues. This will
require N+1 vs N RPC's as compared to the proposed method.
It's preferable to keep the metastore API simple, so I'm a little hesitant to
put in both approaches. If the currently proposed method is fast enough, then
it'd be okay to leave it the way it is.
> Add more calls to the metastore thrift interface
> ------------------------------------------------
>
> Key: HIVE-1788
> URL: https://issues.apache.org/jira/browse/HIVE-1788
> Project: Hive
> Issue Type: New Feature
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Attachments: HIVE-1788.txt
>
>
> For administrative purposes the following calls to the metastore thrift
> interface would be very useful:
> 1. Get the table metadata for all the tables owned by a particular users
> 2. Ability to iterate over this set of tables
> 3. Ability to change a particular key value property of the table
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
