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

Hive QA commented on HIVE-16282:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12860495/HIVE-16282.5.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 10511 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[comments] (batchId=35)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/4355/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/4355/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-4355/

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

This message is automatically generated.

ATTACHMENT ID: 12860495 - PreCommit-HIVE-Build

> Semijoin: Disable slow-start for the bloom filter aggregate task
> ----------------------------------------------------------------
>
>                 Key: HIVE-16282
>                 URL: https://issues.apache.org/jira/browse/HIVE-16282
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Gopal V
>            Assignee: Deepak Jaiswal
>         Attachments: extended plan.rtf, HIVE-16282.1.patch, 
> HIVE-16282.2.patch, HIVE-16282.3.patch, HIVE-16282.4.patch, HIVE-16282.5.patch
>
>
> The slow-start of the bloom filter vertex is a scheduling problem which 
> causes more pre-emption than is useful.
> When the bloom filters are arranged as follows
> Map 1(10 tasks)->Reducer 2(1 task)->Map 3(100 tasks)
> Map 3 and Map 1 are immediately active since Reducer 2 -> Map 3 is a 
> broadcast edge.
> Once 3 tasks in Map 1 finish, the engine kills one active task from Map 3 to 
> make room for Reducer 2.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to