hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aihua Xu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-15498) sum() over (order by c) should default the windowing spec to RangeBoundarySpec
Date Thu, 22 Dec 2016 17:48:58 GMT

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

Aihua Xu updated HIVE-15498:
----------------------------
    Description: 
Currently {{sum() over (partition by a)}} without order by is defaulted windowing to RangeBoundarySpec
while  {{sum() over (partition by a order by c)}} is defaulted to ValueBoundarySpec.

>From the comment 
{noformat}
  /*
   * - A Window Frame that has only the /start/boundary, then it is interpreted as:
         BETWEEN <start boundary> AND CURRENT ROW
   * - A Window Specification with an Order Specification and no Window
   *   Frame is interpreted as:
         ROW BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW
   * - A Window Specification with no Order and no Window Frame is interpreted as:
         ROW BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
   */
{noformat}
We intended to set as "row between" (RangeBoundarySpec), not "range between" (ValueBoundarySpec).



  was:
Currently {{sum() over (partition by a)}} without order by is defaulted windowing to RangeBoundarySpec
while  {{sum() over (partition by a order by c)}} is defaulted to ValueBoundarySpec.

>From the comment 
{noformat}
  /*
   * - A Window Frame that has only the /start/boundary, then it is interpreted as:
         BETWEEN <start boundary> AND CURRENT ROW
   * - A Window Specification with an Order Specification and no Window
   *   Frame is interpreted as:
         ROW BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW
   * - A Window Specification with no Order and no Window Frame is interpreted as:
         ROW BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
   */
{noformat}
We intended to set as "row between", not "range between". 



> sum() over (order by c) should default the windowing spec to RangeBoundarySpec
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-15498
>                 URL: https://issues.apache.org/jira/browse/HIVE-15498
>             Project: Hive
>          Issue Type: Bug
>          Components: PTF-Windowing
>    Affects Versions: 2.1.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>         Attachments: HIVE-15498.1.patch
>
>
> Currently {{sum() over (partition by a)}} without order by is defaulted windowing to
RangeBoundarySpec while  {{sum() over (partition by a order by c)}} is defaulted to ValueBoundarySpec.
> From the comment 
> {noformat}
>   /*
>    * - A Window Frame that has only the /start/boundary, then it is interpreted as:
>          BETWEEN <start boundary> AND CURRENT ROW
>    * - A Window Specification with an Order Specification and no Window
>    *   Frame is interpreted as:
>          ROW BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW
>    * - A Window Specification with no Order and no Window Frame is interpreted as:
>          ROW BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
>    */
> {noformat}
> We intended to set as "row between" (RangeBoundarySpec), not "range between" (ValueBoundarySpec).




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

Mime
View raw message