[
https://issues.apache.org/jira/browse/HIVE-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156030#comment-16156030
]
Zach Amsden commented on HIVE-17429:
------------------------------------
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14] looks like
a difference in test output caused by a WARNING line output in different order.
Running org.apache.hadoop.hive.cli.TestAccumuloCliDriver definitely looks like
a timeout, this is the last output from Maven:
{noformat}
[INFO]
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @
hive-it-qfile-accumulo ---
[INFO] Surefire report directory:
/home/hiveptest/35.193.110.99-hiveptest-0/apache-github-source-source/itests/qtest-accumulo/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.hadoop.hive.cli.TestAccumuloCliDriver
{noformat}
> 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)
