[
https://issues.apache.org/jira/browse/HIVE-20897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702542#comment-16702542
]
Daniel Dai commented on HIVE-20897:
-----------------------------------
OperationStatus.hasResultSet should be false if resultset hasn't been set. Then
we don't have to introduce a backward incompatible null flag over the thrift,
right?
> TestJdbcDriver2#testSelectExecAsync2 fails with result set not present error
> ----------------------------------------------------------------------------
>
> Key: HIVE-20897
> URL: https://issues.apache.org/jira/browse/HIVE-20897
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-20897.01.patch, HIVE-20897.02.patch,
> HIVE-20897.03.patch, HIVE-20897.04.patch, HIVE-20897.05.patch,
> HIVE-20897.06.patch, HIVE-20897.07.patch, HIVE-20897.08.patch
>
>
> if async prepare is enabled, control will be returned to the client before
> driver could set of the query has a result set or not. But in current code,
> while generating the response for the query, it is not checked if the result
> set field is set or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
