[ 
https://issues.apache.org/jira/browse/HIVE-9074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250365#comment-14250365
 ] 

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:
https://issues.apache.org/jira/secure/attachment/12687772/HIVE-9074.patch

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 6713 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver_optimize_nullscan
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2112/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2112/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-2112/

Messages:
{noformat}
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
{noformat}

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: https://issues.apache.org/jira/browse/HIVE-9074
>             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
(v6.3.4#6332)

Reply via email to