[
https://issues.apache.org/jira/browse/HIVE-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629235#comment-13629235
]
Prasad Mujumdar commented on HIVE-4171:
---------------------------------------
[~thejas] Its not specific to 'default' database right ? You can switching to
any database by setting a config instead of executing {{use <db>}}. As
mentioned earlier, there are semantic and exec hooks besides authorization.
These could be used for auditing etc. which will also get bypassed
One of the options could be to restrict the {{set hive.current.db ..}} by
adding this new config to the {{HiveConf.restrictList}} during initialization.
It will prohibit users from changing the current db using the {{set}} command.
Does that sound viable option to include in your patch ?
> Current database in metastore.Hive is not consistent with SessionState
> ----------------------------------------------------------------------
>
> Key: HIVE-4171
> URL: https://issues.apache.org/jira/browse/HIVE-4171
> Project: Hive
> Issue Type: Bug
> Components: CLI
> Reporter: Navis
> Assignee: Thejas M Nair
> Labels: HiveServer2
> Attachments: HIVE-4171.3.patch, HIVE-4171.D9399.1.patch,
> HIVE-4171.D9399.2.patch
>
>
> metastore.Hive is thread local instance, which can have different status with
> SessionState. Currently the only status in metastore.Hive is database name in
> use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
