[
https://issues.apache.org/jira/browse/HIVE-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155693#comment-16155693
]
Zach Amsden commented on HIVE-17429:
------------------------------------
Hmm, these test failures seem to indicate possible timeouts, but missing .xml
files could also indicate that metadata wasn't picked up. Can someone from
Hive take a quick look and see if these might be expected failures?
> Hive JDBC doesn't return rows when querying Impala
> --------------------------------------------------
>
> Key: HIVE-17429
> URL: https://issues.apache.org/jira/browse/HIVE-17429
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 2.1.0
> Reporter: Zach Amsden
> Assignee: Zach Amsden
> Fix For: 2.1.0
>
> Attachments: HIVE-17429.1.patch, HIVE-17429.2.patch
>
>
> The Hive JDBC driver used to return a result set when querying Impala. Now,
> instead, it gets data back but interprets the data as query logs instead of a
> resultSet. This causes many issues (we see complaints about beeline as well
> as test failures).
> This appears to be a regression introduced with asynchronous operation
> against Hive.
> Ideally, we could make both behaviors work. I have a simple patch that
> should fix the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
