[
https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
N Campbell updated HIVE-5460:
-----------------------------
Description:
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
was:
ISO-SQL 2012 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
> 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
>
> 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)
