[
https://issues.apache.org/jira/browse/HIVE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709761#comment-13709761
]
Sivaramakrishnan Narayanan commented on HIVE-4226:
--------------------------------------------------
FYI - I ran into
[this|http://mail-archives.apache.org/mod_mbox/hive-dev/201302.mbox/%3CCA+FBdFR9J4wZZhGDW4aQ66G8+vq2PauTqE=z1kapyerdrpc...@mail.gmail.com%3E]
problem. Fortunately, the solution in the email chain worked for me.
> Cleanup non-threadsafe code in Hive
> -----------------------------------
>
> Key: HIVE-4226
> URL: https://issues.apache.org/jira/browse/HIVE-4226
> Project: Hive
> Issue Type: Improvement
> Reporter: Sivaramakrishnan Narayanan
> Assignee: Sivaramakrishnan Narayanan
> Attachments: HIVE-4226.1.patch.txt, HIVE-4226.2.patch.txt,
> HIVE-4226.D11703.1.patch
>
>
> There is some code in Hive that is not threadsafe. These usually bubble up as
> problems in Hive Server. This JIRA tracks fixing (hopefully, all) of these
> issues.
> Some context: we've implemented a multi-tenant (multiple dbs), multi-threaded
> hive server at Qubole (QHS) which is running in production for a couple of
> months now. As part of this effort, we've fixed a number of instances of
> non-threadsafe code. I'm looking to contribute this back to the community.
> Note that there is no new functionality here - just some better hygiene. If
> there are any stress tests that have revealed hive server bugs in the past,
> it will be great if they can be added to the jira.
> Also, this is my first attempt at contributing to Apache, so please forgive
> any mistakes.
--
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
