[JBoss JIRA] (TEIID-3931) Add support for odata service geospatial handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3931:
---------------------------------------
Given the added importance to odata I'm going to take a fresh look at this to see if we can have more robust support.
> Add support for odata service geospatial handling
> -------------------------------------------------
>
> Key: TEIID-3931
> URL: https://issues.jboss.org/browse/TEIID-3931
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.2
>
>
> We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5478) Add engine support for nth_value
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5478:
-------------------------------------
Summary: Add engine support for nth_value
Key: TEIID-5478
URL: https://issues.jboss.org/browse/TEIID-5478
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.2
Due to TEIID-5475 engine support for nth_value was removed. It should be added back with frame clause support.
--
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 resolved TEIID-5475.
-----------------------------------
Resolution: Done
Resolved by removing engine support for now. Will add corrected support later.
> 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... ]
Work on TEIID-5475 started by Steven Hawkins.
---------------------------------------------
> 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-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 resolved TEIID-5477.
-----------------------------------
Resolution: Done
Addressed by computing over all rows instead of using the range indexing. The fix is slightly different for each branch due to the evolving logic. For back port start with the 10.3.5 patch.
> 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