[
https://issues.apache.org/jira/browse/HIVE-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565124#comment-14565124
]
Chaoyu Tang commented on HIVE-10835:
------------------------------------
Thanks [~sershe] for the information and noticed that you are already working
on HIVE-4239.
This JIRA mainly addresses the concurrency issue at client site (JDBC driver)
while HIVE-4239 may focus on server site as I understand, so I think they could
be considered as separate issues. We are working together to address the races
in the system but from different areas. Could you take a look at the patch and
comment, thanks.
> Concurrency issues in JDBC driver
> ---------------------------------
>
> Key: HIVE-10835
> URL: https://issues.apache.org/jira/browse/HIVE-10835
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 1.2.0
> Reporter: Chaoyu Tang
> Assignee: Chaoyu Tang
> Attachments: HIVE-10835.1.patch, HIVE-10835.2.patch, HIVE-10835.patch
>
>
> Though JDBC specification specifies that "Each Connection object can create
> multiple Statement objects that may be used concurrently by the program", but
> that does not work in current Hive JDBC driver. In addition, there also exist
> race conditions between DatabaseMetaData, Statement and ResultSet as long as
> they make RPC calls to HS2 using same Thrift transport, which happens within
> a connection.
> So we need a connection level lock to serialize all these RPC calls in a
> connection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
