hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "He Yongqiang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-908) optimize limit
Date Thu, 29 Oct 2009 21:23:59 GMT

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

He Yongqiang commented on HIVE-908:
-----------------------------------

HIVE-588.
Is this issue the same as HIVE-588?

> optimize limit
> --------------
>
>                 Key: HIVE-908
>                 URL: https://issues.apache.org/jira/browse/HIVE-908
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Namit Jain
>             Fix For: 0.5.0
>
>
> If there is a limit, all the mappers have to finish and create 'limit' number of rows
- this can be pretty expensive for a large file.
> The following optimizations can be performed in this area:
> 1. Start fewer mappers if there is a limit - before submitting a job, the compiler knows
that there is a limit - so, it might be useful to increase the split size, thereby reducing
the number of mappers.
> 2. A counter is maintained for the total outputs rows - the mappers can look at those
counters and decide to exit instead of emitting 'limit' number of rows themselves.
> 2. may lead to some bugs because of bugs in counters, but 1. should definitely help

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message