[
https://issues.jboss.org/browse/TEIID-5477?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-5477:
----------------------------------
Description:
LEAD/LAG should be computed as row values functions, rather than over a range.
for example:
select e1, lead(e1, 2) over (order by e1 nulls last) from pm1.g1
returns three rows of ('a', 'c') - rather than the expected ('a',
'a'), ('a', 'b'), ('a', 'c')
was:
LEAD/LAG should be computed as row values functions, rather than over a range.
for example:
select e1, lead(e1, 2) over (order by e1 nulls last) from pm1.g1
returns three rows of ('a', 'a') - rather than the expected ('a',
'a'), ('a', 'b'), ('a', 'c')
Incorrect results with lead/lag over windows with duplicates
------------------------------------------------------------
Key: TEIID-5477
URL:
https://issues.jboss.org/browse/TEIID-5477
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.2, 11.1.1, 11.0.3, 10.3.5
LEAD/LAG should be computed as row values functions, rather than over a range.
for example:
select e1, lead(e1, 2) over (order by e1 nulls last) from pm1.g1
returns three rows of ('a', 'c') - rather than the expected ('a',
'a'), ('a', 'b'), ('a', 'c')
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)