hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
Date Mon, 07 Oct 2013 15:16:42 GMT

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

Edward Capriolo commented on HIVE-5460:
---------------------------------------

99% of the windowing merge violated our code conventions. I am slowly fixing these issues
as we find bugs and other tweeks in the code. You know next time someone does a code pie chart
about a release I want to have the most lines of code :)

> 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)

Mime
View raw message