[
https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277087#comment-13277087
]
Carl Steinbach commented on HIVE-3016:
--------------------------------------
bq. Example: user A will have access to data in database db1 as well as db2.
When in the context of db1, we don't want them to use data from db2. When in
the context of db2, they can indeed use data from db2. The goal is to contain
all access when in the context of a database to just data in that database.
I'm having a hard time understanding why you would want to enforce this
restriction. What's the motivation for doing this?
> 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
