[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623336#comment-15623336
]
Sergey Shelukhin commented on HIVE-15062:
-----------------------------------------
Thanks for the feedback.
I have added the usage guidelines in the exception text; the setting is also
settable from the client (added that to the error message now), so such tools
should be able to set it per session.
I don't think there's a way around this for external tools - at worst, they
will have to disable this globally, which is no worse than the current
situation, or they can disable it per session. However, we would have proper
handling for different versions of Hive, such as in heterogeneous clusters and
for rolling upgrade.
> 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.03.nogen.patch,
> HIVE-15062.03.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)
