hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bc Wong (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HIVE-1261) ql.metadata.Hive#close() should check for null metaStoreClient
Date Sat, 20 Mar 2010 09:11:27 GMT

     [ https://issues.apache.org/jira/browse/HIVE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

bc Wong updated HIVE-1261:
--------------------------

    Assignee: bc Wong
      Status: Patch Available  (was: Open)

> 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
>         Attachments: HIVE-1261-1.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.


Mime
View raw message