[
https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277957#comment-13277957
]
Edward Capriolo commented on HIVE-3016:
---------------------------------------
@Sambavi Hive has this concept of Hooks eg metastore hooks. They are pluggable
classes that receive events at runtime and sometimes can optionally veto them.
If possible you might want to go this route. I am not 100% sure there is a hook
for what you need but Hooks might better place to plug in deployment specific
requirements.
I do understand what you are facing we have DB's for applications and for
users. keeping track of who made what is hard at times. One option a slight
different way to tackle your issue, is you can use the table properties to tag
tables with metadata and your tools can scan this for reporting. Tables are
already tagged with the USER who created them in meta-data as well.
> Allow disabling foreign table access (cross database) using hiveconf
> --------------------------------------------------------------------
>
> Key: HIVE-3016
> URL: https://issues.apache.org/jira/browse/HIVE-3016
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Sambavi Muthukrishnan
> Assignee: Sambavi Muthukrishnan
> Priority: Minor
> Attachments: hive-3016.1.patch.txt
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Disallow cross database access to tables using Y.T syntax under a specific
> configuration in HiveConf.
> i.e. when hive.error.on.crossdatabaseaccess is set to true, return an error
> when Y.T syntax is used to access tables and Y is not the current database.
> This can be set both via the client and in hive-site.xml, and will default to
> false.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
