hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gopal V (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-7397) Set the default threshold for fetch task conversion to 1Gb
Date Sat, 12 Jul 2014 07:05:04 GMT

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

Gopal V commented on HIVE-7397:
-------------------------------

[~navis]: changed the defaults and disabled it for tests.

Also modified the codepath to handle the simple project + limit + partition filter case, even
for a big table.

> Set the default threshold for fetch task conversion to 1Gb
> ----------------------------------------------------------
>
>                 Key: HIVE-7397
>                 URL: https://issues.apache.org/jira/browse/HIVE-7397
>             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
>
>
> 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
table.
> 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
(v6.2#6252)

Mime
View raw message