[
https://issues.apache.org/jira/browse/HIVE-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597331#comment-13597331
]
Phabricator commented on HIVE-4126:
-----------------------------------
ashutoshc has accepted the revision "HIVE-4126 [jira] remove support for
lead/lag UDFs outside of UDAF args".
+1
INLINE COMMENTS
common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:732 1MB sounds too
low. How about 25 MB? If you agree, I will just edit this line while committing
it.
REVISION DETAIL
https://reviews.facebook.net/D9105
BRANCH
HIVE-4126
ARCANIST PROJECT
hive
To: JIRA, ashutoshc, hbutani
> remove support for lead/lag UDFs outside of UDAF args
> -----------------------------------------------------
>
> Key: HIVE-4126
> URL: https://issues.apache.org/jira/browse/HIVE-4126
> Project: Hive
> Issue Type: Bug
> Components: PTF-Windowing
> Reporter: Harish Butani
> Assignee: Harish Butani
> Attachments: HIVE-4126.D9105.1.patch, HIVE-4126.D9105.2.patch
>
>
> Select Expressions such as
> p_size - lead(p_size,1)
> are currently handled as non aggregation expressions done after all over
> clauses are evaluated.
> Once we allow different partitions in a single select list(Jira 4041), these
> become ambiguous.
> - the equivalent way to do such things is either to use lead/lag UDAFs with
> expressions ( support added with Jira 4081)
> - stack windowing clauses with inline queries. select lead(r,1).. from
> (select rank() as r....)...
--
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
