[
https://issues.apache.org/jira/browse/HIVE-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-5381:
------------------------------
Attachment: D13161.1.patch
navis requested code review of "HIVE-5381 [jira] OOM when using many lead/lag
funtions against large partition".
Reviewers: JIRA
HIVE-5381 OOM when using many lead/lag funtions against large partition
Currently, columns containing window function are evaluated for all rows in a
partition, which possibly make OOM if the partition is big (400MB in my case).
For lead/lag functions, the value can be evaluated per row.
TEST PLAN
EMPTY
REVISION DETAIL
https://reviews.facebook.net/D13161
AFFECTED FILES
ql/src/java/org/apache/hadoop/hive/ql/exec/LLRowResolver.java
ql/src/java/org/apache/hadoop/hive/ql/exec/PTFPartition.java
ql/src/java/org/apache/hadoop/hive/ql/udf/ptf/WindowingTableFunction.java
MANAGE HERALD RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/38499/
To: JIRA, navis
> OOM when using many lead/lag funtions against large partition
> -------------------------------------------------------------
>
> Key: HIVE-5381
> URL: https://issues.apache.org/jira/browse/HIVE-5381
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: D13161.1.patch
>
>
> Currently, columns containing window function are evaluated for all rows in a
> partition, which possibly make OOM if the partition is big (400MB in my
> case). For lead/lag functions, the value can be evaluated per row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
