[
https://issues.apache.org/jira/browse/HIVE-21838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Gangam updated HIVE-21838:
---------------------------------
Status: Patch Available (was: Open)
Patch includes:
1) Adding {{RequiredReadCapabilities}} and {{RequiredWriteCapabilities}} to the
Table object that passback capabilities required to gain certain access to that
Table. For example, when the table.getAccessType == READONLY,
table.getRequiredWriteCapabilities() will contain a list of capabilities
required to gain READWRITE access to that table. Because the access is already
READONLY, getRequiredReadCapabilities() will be null.
When the accessType==NONE, then getRequiredReadCapabilities and
getRequiredWriteCapabilities will be non-null.
2) Adding a CreateTableRequest that will be used by all create_table calls. The
processorCapabilities will now be passed in to the HMS for create_table
requests. A client attempting to create an ACID table without possessing the
appropriate WRITE capability will now fail.
All create_table requests for non-ACID tables of type MANAGED_TABLE will now be
converted to EXTERNAL_TABLE types automatically.
3) New tests to cover create_table scenarios.
> 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: Sub-task
> Reporter: Yongzhi Chen
> Assignee: Naveen Gangam
> Priority: Major
> Attachments: HIVE-21838.patch
>
>
> 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)
