[
https://issues.apache.org/jira/browse/HIVE-13088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152992#comment-15152992
]
Sergio Peña commented on HIVE-13088:
------------------------------------
This patch will display an error message on console and the surefire output
files like this:
{code}
Running org.apache.hadoop.hive.cli.TestCliDriver
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 89.254 sec <<<
FAILURE! - in org.apache.hadoop.hive.cli.TestCliDriver
testCliDriver_analyze_tbl_part(org.apache.hadoop.hive.cli.TestCliDriver) Time
elapsed: 16.314 sec <<< FAILURE!
java.lang.AssertionError: Unexpected exception java.lang.AssertionError:
"Invalid partitioning key/value specified in ANALYZE statement"
command=[ANALYZE TABLE src_stat_string_part partition (partitionName="p'1")
COMPUTE STATISTICS for columns key, value] errorCode=[30007] debugHint=[See
./ql/target/tmp/log/hive.log or ./itests/qtest/target/tmp/log/hive.log, or
check ./ql/target/surefire-reports or ./itests/qtest/target/surefire-reports/
for specific test cases logs.]
at org.junit.Assert.fail(Assert.java:88)
at org.apache.hadoop.hive.ql.QTestUtil.failed(QTestUtil.java:2006)
{code}
The stacktrace is still the same generic error, but that is because we use
Assert.fail() to make the test case fail, and this prints such stack trace.
> Display correct error message on QTest failure commands
> -------------------------------------------------------
>
> Key: HIVE-13088
> URL: https://issues.apache.org/jira/browse/HIVE-13088
> Project: Hive
> Issue Type: Improvement
> Components: Testing Infrastructure
> Affects Versions: 1.2.1, 2.0.0
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Priority: Minor
> Attachments: HIVE-13088.1.patch
>
>
> Everytime a QTest command fails, a generic error message is displayed on
> console and surefire-output files. This does not help to understand the error
> at all.
> We should display the correct error message that Hive throws to troubleshoot
> the issue faster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
