[ https://issues.apache.org/jira/browse/HIVE-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780103#comment-13780103 ]
Hive QA commented on HIVE-5381: ------------------------------- {color:green}Overall{color}: +1 all checks pass Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12605413/D13161.1.patch {color:green}SUCCESS:{color} +1 3176 tests passed Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/936/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/936/console Messages: {noformat} Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase {noformat} This message is automatically generated. > 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