You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Li Jin (JIRA)" <ji...@apache.org> on 2018/04/04 02:23:00 UTC

[jira] [Created] (SPARK-23861) Clarify behavior of default window frame boundaries with and without orderBy clause

Li Jin created SPARK-23861:
------------------------------

             Summary: 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


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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org