You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Peter Vary (JIRA)" <ji...@apache.org> on 2017/04/24 15:14:04 UTC

[jira] [Created] (HIVE-16517) HiveStatement thread safety issues

Peter Vary created HIVE-16517:
---------------------------------

             Summary: HiveStatement thread safety issues
                 Key: HIVE-16517
                 URL: https://issues.apache.org/jira/browse/HIVE-16517
             Project: Hive
          Issue Type: Bug
            Reporter: Peter Vary


{{BeeLine}}, and {{Commands}} classes shares one HiveStatement between multiple threads for querying the logs, and running the queries.

We can not make the HiveStatement thread safe, but we should at least make sure that calling {{getQueryLog}} will not cause problems if it is called parallel with any of the followings: {{cancel}}, {{close}}, {{execute}}, {{executeAsync}}, {{executeQuery}}, {{executeUpdate}}, {{getUpdateCount}} and more interestingly for the {{HiveQueryResultSet.next}} too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)