hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-15498) sum() over (order by c) should default the windowing spec to RangeBoundarySpec
Date Fri, 23 Dec 2016 00:40:58 GMT

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

Hive QA commented on HIVE-15498:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12844469/HIVE-15498.2.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 10895 tests executed
*Failed tests:*
{noformat}
TestDerbyConnector - did not produce a TEST-*.xml file (likely timed out) (batchId=234)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_4] (batchId=93)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/2704/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/2704/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-2704/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12844469 - PreCommit-HIVE-Build

> 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, HIVE-15498.2.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.
It's not consistent and the user gets confused of the switch from "rows between" to "range
between" by adding "order by c" clause.
> 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