hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-9074) add ability to force direct sql usage for perf reasons
Date Wed, 17 Dec 2014 19:27:13 GMT


Hive QA commented on HIVE-9074:

{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), 6713 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

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

This message is automatically generated.

ATTACHMENT ID: 12687772 - PreCommit-HIVE-TRUNK-Build

> add ability to force direct sql usage for perf reasons
> ------------------------------------------------------
>                 Key: HIVE-9074
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>         Attachments: HIVE-9074.patch
> Some people run direct SQL and hit failures (e.g. due to Oracle 1000-in-expressions stupidity,
illegal cast "optimization" in Derby and Oracle, or some other Hive and DB bugs). Currently,
it falls back to ORM for such cases, however that can have huge impact on perf, and some people
would rather have it fail so they can see the problem.
> In addition to "off" and "on+fallback" modes, "on or fail" mode needs to be added. The
default will remain the same.

This message was sent by Atlassian JIRA

View raw message