[
https://issues.apache.org/jira/browse/HIVE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Steinbach updated HIVE-1261:
---------------------------------
Fix Version/s: 0.6.0
> ql.metadata.Hive#close() should check for null metaStoreClient
> --------------------------------------------------------------
>
> Key: HIVE-1261
> URL: https://issues.apache.org/jira/browse/HIVE-1261
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: bc Wong
> Assignee: bc Wong
> Fix For: 0.6.0
>
> Attachments: HIVE-1261-1.patch, HIVE-1261-2.patch
>
>
> {{ql.metadata.Hive#close()}} always does a {{metaStoreClient.close()}}, even
> though it might be null.
> I'd like to reuse the same thread for multiple queries from different users.
> Since it's a different user, {{HiveConf}} has a new ugi. But it's not easy to
> get rid of (or update) the cached {{ql.metadata.Hive}}. The cleanest way
> seems to be {{Hive.closeCurrent()}}, which unfortunately doesn't check for
> the {{metaStoreClient}} being {{null}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
