hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-12956) run CBO in tests with mapred.mode=strict
Date Sat, 30 Jan 2016 20:24:39 GMT


Hive QA commented on HIVE-12956:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

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

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 8 tests failed

This message is automatically generated.

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

> run CBO in tests with mapred.mode=strict
> ----------------------------------------
>                 Key: HIVE-12956
>                 URL:
>             Project: Hive
>          Issue Type: Test
>            Reporter: Sergey Shelukhin
>            Assignee: Ashutosh Chauhan
>         Attachments: HIVE-12956.2.patch, HIVE-12956.patch
> There's a strange condition in CBO check that prevents CBO from running in Hive tests
(in tests specifically) when mapred.mode is set to strict. I remember seeing it before, and
noticed it again recently.
> It is both surprising that we wouldn't test CBO in strict mode, and also problematic
for some q files because strict mode is going to be deprecated in HIVE-12727. This needs to
be removed.

This message was sent by Atlassian JIRA

View raw message