hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4171) Current database in metastore.Hive is not consistent with SessionState
Date Thu, 11 Apr 2013 18:13:39 GMT

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

Thejas M Nair commented on HIVE-4171:
-------------------------------------

[~prasadm] I agree that we should be careful about storing runtime state in HiveConf because
of the above reason. But in case of default database setting, does authorization make sense
? Setting default database does not perform any action. It is just saying that for your other
commands use this database as default. It is during the execution of other commands (eg 'show
tables;' or 'select * from tabl;') when authorization checks would need to kick in.

                
> 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

Mime
View raw message