[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613488#comment-15613488
]
Thejas M Nair commented on HIVE-15062:
--------------------------------------
Some notes on the feature after discussion with Sergey
* The current api would call the new API will NULL for the capabilities
* This give an error only if the table being accessed has additional
capabilities that client should have to be able to access the data correctly.
[~sershe]
* Enum have been causing issues in HiveServer2. See HIVE-6050
* Call the current VERSION capability NULL_VERSION or so ?
> create backward compat checking for metastore APIs
> --------------------------------------------------
>
> Key: HIVE-15062
> URL: https://issues.apache.org/jira/browse/HIVE-15062
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch,
> HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.nogen.patch,
> HIVE-15062.patch
>
>
> This is to add client capability checking to Hive metastore.
> This could have been used, for example, when introducing ACID tables - a
> client trying to get_table on such a table without specifying that it is
> aware of ACID tables would get an error by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
