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

Hive QA commented on HIVE-5460:
-------------------------------



{color:red}Overall{color}: -1 at least one tests failed

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

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 4060 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1064/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1064/console

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

This message is automatically generated.

> invalid offsets in lag lead should return an exception (per ISO-SQL) 
> ---------------------------------------------------------------------
>
>                 Key: HIVE-5460
>                 URL: https://issues.apache.org/jira/browse/HIVE-5460
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.11.0
>            Reporter: N Campbell
>            Assignee: Edward Capriolo
>            Priority: Minor
>         Attachments: HIVE-5460.1.patch.txt
>
>
> ISO-SQL 2011 defines how lag and lead should behave when invalid offsets are 
> provided to the functions.
> i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 )  over ( order by 
> tint.rnum) from tint tint 
> Instead of a meaningful error (as other vendors will emit) you get 
> Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, 
> return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask
> SQLState:  08S01
> ErrorCode: 2



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to