You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Naveen Gangam (JIRA)" <ji...@apache.org> on 2019/06/07 14:36:00 UTC
[jira] [Commented] (HIVE-21838) Hive Metastore Translation: Add API
call to tell client why table has limited access
[ https://issues.apache.org/jira/browse/HIVE-21838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858705#comment-16858705 ]
Naveen Gangam commented on HIVE-21838:
--------------------------------------
[~ychena] There are a couple of options here
1) Expand the Table thrift object to include a new List to indicate the expected capabilities for this table to get "full" access (its different for different TableTypes, Virtual views can only have RO access at best). We are a bit worried about adding another field to the Table object that could increase the footprint of the objects across the wire, particularly for getTables* apis that return uncapped sets of Table's.
2) Alternatively, we could used the Table.getProperties() to introduce a new key or re-use "OBJCAPABILITIES" that we have introduced for creating tables with capabilities. These properties would be passed back anyways for tables that have defined capabilities when they were created.
We will discuss these options and keep you posted. Thanks
> Hive Metastore Translation: Add API call to tell client why table has limited access
> ------------------------------------------------------------------------------------
>
> Key: HIVE-21838
> URL: https://issues.apache.org/jira/browse/HIVE-21838
> Project: Hive
> Issue Type: New Feature
> Reporter: Yongzhi Chen
> Assignee: Naveen Gangam
> Priority: Major
>
> When a table access type is Read-only or None, we need a way to tell clients why.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)