[JBoss JIRA] (TEIID-5472) Clean up window function project node implementation
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5472?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5472:
---------------------------------------
Another clean up is to refactor so that the differentiation between range and rows is done when saving values, not in differentiating the window specifications.
> Clean up window function project node implementation
> ----------------------------------------------------
>
> Key: TEIID-5472
> URL: https://issues.jboss.org/browse/TEIID-5472
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.2
>
>
> The initial implementation of window functions did not allow for a frame clause and specifically separated the logic of creating row and range values. Now that the logic is more complete we should remove some of the initial design aspects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5477) Incorrect results with lead/lag over windows with duplicates
by Steven Hawkins (JIRA)
[ 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)
6 years, 4 months
[JBoss JIRA] (TEIID-5477) Incorrect results with lead/lag over windows with duplicates
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5477:
-------------------------------------
Summary: 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', 'a') - rather than the expected ('a', 'a'), ('a', 'b'), ('a', 'c')
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5476) Teiid Embedded brings in JGroups dependency implicitly
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5476?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-5476:
--------------------------------
Summary: Teiid Embedded brings in JGroups dependency implicitly (was: Teiid Embedded bring in JGroups dependency implicitly)
> Teiid Embedded brings in JGroups dependency implicitly
> ------------------------------------------------------
>
> Key: TEIID-5476
> URL: https://issues.jboss.org/browse/TEIID-5476
> Project: Teiid
> Issue Type: Enhancement
> Components: Embedded
> Reporter: Ramesh Reddy
>
> Teiid Embedded brings in the JGroups dependency implicitly even when there is no clustering is required by the user. This adds about 2.5MB to the size.
> Irrespective of the size, with the move to container kind of workloads, this should be enhanced such that it is an additional layer rather than part of the core layer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5476) Teiid Embedded bring in JGroups dependency implicitly
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-5476:
-----------------------------------
Summary: Teiid Embedded bring in JGroups dependency implicitly
Key: TEIID-5476
URL: https://issues.jboss.org/browse/TEIID-5476
Project: Teiid
Issue Type: Enhancement
Components: Embedded
Reporter: Ramesh Reddy
Teiid Embedded brings in the JGroups dependency implicitly even when there is no clustering is required by the user. This adds about 2.5MB to the size.
Irrespective of the size, with the move to container kind of workloads, this should be enhanced such that it is an additional layer rather than part of the core layer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5475) nth_value is incorrect for some initial values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5475?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5475:
----------------------------------
Description:
Nth_value is returning null when not expected. For example:
select e1, nth_value(e1, 2) over (order by e1 nulls last) from g1
with our default data set should return 'a' for each nth_value, but instead returns null for one of the 'a' rows. The issue is that we should be considering the indexing to be relative from the start of the peer group in the frame rather than from the current index of the row.
was:
Nth_value is returning null when not expected. For example:
select e1, nth_value(e1, 2) over (order by e1) from pm1.g1
with our default data set should return 'a' for each nth_value, but instead returns null for one of the 'a' rows. The issue is that we should be considering the indexing to be relative from the start of the peer group in the frame rather than from the current index of the row.
> nth_value is incorrect for some initial values
> ----------------------------------------------
>
> Key: TEIID-5475
> URL: https://issues.jboss.org/browse/TEIID-5475
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 11.2, 11.1.1
>
>
> Nth_value is returning null when not expected. For example:
> select e1, nth_value(e1, 2) over (order by e1 nulls last) from g1
> with our default data set should return 'a' for each nth_value, but instead returns null for one of the 'a' rows. The issue is that we should be considering the indexing to be relative from the start of the peer group in the frame rather than from the current index of the row.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5475) nth_value is incorrect for some initial values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5475?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5475:
----------------------------------
Summary: nth_value is incorrect for some initial values (was: nth_value is incorrect for )
> nth_value is incorrect for some initial values
> ----------------------------------------------
>
> Key: TEIID-5475
> URL: https://issues.jboss.org/browse/TEIID-5475
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 11.2, 11.1.1
>
>
> Nth_value is returning null when not expected. For example:
> select e1, nth_value(e1, 2) over (order by e1) from pm1.g1
> with our default data set should return 'a' for each nth_value, but instead returns null for one of the 'a' rows. The issue is that we should be considering the indexing to be relative from the start of the peer group in the frame rather than from the current index of the row.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months