[ 
https://issues.apache.org/jira/browse/SPARK-23861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyukjin Kwon resolved SPARK-23861.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.0

Issue resolved by pull request 20978
[https://github.com/apache/spark/pull/20978]

> Clarify behavior of default window frame boundaries with and without orderBy 
> clause
> -----------------------------------------------------------------------------------
>
>                 Key: SPARK-23861
>                 URL: https://issues.apache.org/jira/browse/SPARK-23861
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.3.0
>            Reporter: Li Jin
>            Assignee: Li Jin
>            Priority: Minor
>             Fix For: 2.4.0
>
>
> Without an orderBy clause, the default window frame boundary is (rowFrame, 
> unbounded, unbouned). With an orderBy clause, the default window frame 
> boundary is (rangeFrame, unbouned, currentRow). This behavior is by design 
> but is a bit intuitive to people that are not very familiar with SQL window 
> semantics. Let's update the API doc to clarify that.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to