You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zhihua Deng (Jira)" <ji...@apache.org> on 2021/03/13 03:11:00 UTC
[jira] [Commented] (HIVE-24861) Hive JDBC driver doesn't consider
the value of 'hasMoreRows'
[ https://issues.apache.org/jira/browse/HIVE-24861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300690#comment-17300690 ]
Zhihua Deng commented on HIVE-24861:
------------------------------------
Hi [~boroknagyz], I try to propose a patch, but unsure to fix your problem, cloud you please try it?
> Hive JDBC driver doesn't consider the value of 'hasMoreRows'
> ------------------------------------------------------------
>
> Key: HIVE-24861
> URL: https://issues.apache.org/jira/browse/HIVE-24861
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Reporter: Zoltán Borók-Nagy
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> TCLIService's FetchResults might return an empty result set, but with hasMoreRows=true. In that case the driver ignores the flag hasMoreRows and thinks it is the end of the result stream, causing data loss.
> I've seen this when the Hive JDBC driver was used to connect to Impala. IMPALA-7312 introduced a timeout on FetchResults(). If Impala cannot produce rows in the given timeout then it returns an empty result set, but setting hasMoreRows=true. However, the Hive JDBC driver interprets it as the end of the result stream and closes the operation.
> I think if hasMoreRows=true then the Hive JDBC driver should issue FetchResults() again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)