You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jason Dere (JIRA)" <ji...@apache.org> on 2018/06/14 18:18:00 UTC

[jira] [Commented] (HIVE-19898) Disable TransactionalValidationListener when the table is not in the Hive catalog

    [ https://issues.apache.org/jira/browse/HIVE-19898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512843#comment-16512843 ] 

Jason Dere commented on HIVE-19898:
-----------------------------------

A quick fix is to update the TransactionalValidationListener to check the table's catalog name, and only run if the catalog is "hive".

Perhaps longer-term we can think about configuring each catalog to have its own list of PreEventListeners, so the hive catalog would have the TransactionalValidationListener registered, and others can have their own catalog-specific PreEventListeners. This would require being able to retrieve the catalog name from the PreEventContext object.

> Disable TransactionalValidationListener when the table is not in the Hive catalog
> ---------------------------------------------------------------------------------
>
>                 Key: HIVE-19898
>                 URL: https://issues.apache.org/jira/browse/HIVE-19898
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore, Standalone Metastore
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>            Priority: Major
>
> The TransactionalValidationListener does validation of tables specified as transactional tables, as well as enforcing create.as.acid. While this can be useful to Hive, this may not be useful to other catalogs which do not support transactional tables, and would not benefit from being automatically tagged as a transactional table. This should be changed so the TransactionalValidationListener does not run for non-hive catalogs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)