[
https://issues.apache.org/jira/browse/HIVE-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429084#comment-16429084
]
Mark Smith commented on HIVE-17429:
-----------------------------------
Hey [~aihuaxu], just a heads-up that while this fix is in the 2.1.x branch and
master, it's not in the 2.2.x or 2.3.x branches. Since 2.3.x is the latest
release available on maven central just now, it'll probably bite quite a few
people trying to use it with Impala.
I've added the relevant releases to the 'Affects Versions' field, but you may
want to consider porting the fix to 2.3 if you're planning to do any more
releases before 3.0, since it's not really usable with Impala without it.
> 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, 2.2.0, 2.3.0, 2.3.1, 2.3.2
> Reporter: Zach Amsden
> Assignee: Zach Amsden
> Priority: Major
> 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
(v7.6.3#76005)
