[
https://issues.apache.org/jira/browse/HIVE-24861?focusedWorklogId=607467&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-607467
]
ASF GitHub Bot logged work on HIVE-24861:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Jun/21 00:18
Start Date: 06/Jun/21 00:18
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on pull request #2070:
URL: https://github.com/apache/hive/pull/2070#issuecomment-855314871
This pull request has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the d...@hive.apache.org list if the patch is in
need of reviews.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 607467)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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)
