hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-5029) direct SQL perf optimization cannot be tested well (yet)
Date Fri, 09 Aug 2013 06:38:48 GMT


Hive QA commented on HIVE-5029:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 2772 tests executed
*Failed tests:*

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed

This message is automatically generated.
> direct SQL perf optimization cannot be tested well (yet)
> --------------------------------------------------------
>                 Key: HIVE-5029
>                 URL:
>             Project: Hive
>          Issue Type: Test
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Critical
>         Attachments: HIVE-5029.patch
> HIVE-4051 introduced perf optimization that involves getting partitions directly via
SQL in metastore. Given that SQL queries might not work on all datastores (and will not work
on non-SQL ones), JDO fallback is in place.
> Given that perf improvement is very large for short queries, it's on by default.
> However, there's a problem with tests with regard to that. If SQL code is broken, tests
may fall back to JDO and pass. If JDO code is broken, SQL might allow tests to pass.
> We are going to disable SQL by default before the testing problem is resolved.
> There are several possible solultions:
> 1) Separate build for this setting. Seems like an overkill...
> 2) Enable by default; disable by default in tests, create a clone of TestCliDriver with
a subset of queries that will exercise the SQL path.
> 3) Have some sort of test hook inside metastore that will run both ORM and SQL and compare.
> 3') Or make a subclass of ObjectStore that will do that. ObjectStore is already pluggable.
> 4) Write unit tests for one of the modes (JDO, as non-default?) and declare that they
are sufficient; disable fallback in tests.
> 3' seems like the easiest. For now we will disable SQL by default.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message