You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/10/10 01:19:20 UTC

[jira] [Commented] (SPARK-17844) DataFrame API should simplify defining frame boundaries without partitioning/ordering

    [ https://issues.apache.org/jira/browse/SPARK-17844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15560966#comment-15560966 ] 

Apache Spark commented on SPARK-17844:
--------------------------------------

User 'rxin' has created a pull request for this issue:
https://github.com/apache/spark/pull/15412

> DataFrame API should simplify defining frame boundaries without partitioning/ordering
> -------------------------------------------------------------------------------------
>
>                 Key: SPARK-17844
>                 URL: https://issues.apache.org/jira/browse/SPARK-17844
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Reynold Xin
>            Assignee: Reynold Xin
>
> When I was creating the example code for SPARK-10496, I realized it was pretty convoluted to define the frame boundaries for window functions when there is no partition column or ordering column. The reason is that we don't provide a way to create a WindowSpec directly with the frame boundaries. We can trivially improve this by adding rowsBetween and rangeBetween to Window object.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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