hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-7397) Set the default threshold for fetch task conversion to 1Gb
Date Fri, 18 Jul 2014 14:52:05 GMT


Hive QA commented on HIVE-7397:

{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 3 failed/errored test(s), 5740 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: 3 tests failed

This message is automatically generated.


> Set the default threshold for fetch task conversion to 1Gb
> ----------------------------------------------------------
>                 Key: HIVE-7397
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.14.0, 0.13.1
>            Reporter: Gopal V
>            Assignee: Gopal V
>              Labels: Performance
>             Fix For: 0.14.0
>         Attachments: HIVE-7397.1.patch, HIVE-7397.2.patch, HIVE-7397.3.patch, HIVE-7397.4.patch.txt
> Currently, modifying the value of hive.fetch.task.conversion to "more" results in a dangerous
setting where small scale queries function, but large scale queries crash.
> This occurs because the default threshold of -1 means apply this optimization for a petabyte
> I am testing a variety of queries with the setting "more" (to make it the default option
as suggested by HIVE-887) change the default threshold for this feature to a reasonable 1Gb.

This message was sent by Atlassian JIRA

View raw message