July 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4390) Expand level support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4390?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4390: ---------------------------------- Fix Version/s: 8.12.x-6.4 > Expand level support > -------------------- > > Key: TEIID-4390 > URL: https://issues.jboss.org/browse/TEIID-4390 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.x-6.4 > > > We should support the level construct for expand to support recursive relationships. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4385) Nested subquery in an aggregate fails to evaluate

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4385?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4385: ---------------------------------- Fix Version/s: 8.12.x-6.4 > Nested subquery in an aggregate fails to evaluate > ------------------------------------------------- > > Key: TEIID-4385 > URL: https://issues.jboss.org/browse/TEIID-4385 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.3, 8.12.x-6.4, 8.12.12.6_3 > > > A correlated subquery that appears in an aggregate value inside of a subquery, will not have the correlated values available and fail with a TEIID30328 exception. > For example: > SELECT g0.a, g0.b, (SELECT max((SELECT g2.a FROM m.z AS g2 WHERE g2.b = g1.a)) FROM m.y AS g1 WHERE g0.a = g1.b) FROM m.x AS g0 > will fail on the g0.a reference. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4387) Issues with $it support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4387?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4387: ---------------------------------- Fix Version/s: 8.12.x-6.4 > Issues with $it support > ----------------------- > > Key: TEIID-4387 > URL: https://issues.jboss.org/browse/TEIID-4387 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.x-6.4 > > > Only a single $it reference can exist with the current logic, and it can only be used in a filter. With the refactoring to array style logic, we should be able to expand its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4379) OData entity row created twice

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4379?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-4379: ----------------------------------- > OData entity row created twice > ------------------------------ > > Key: TEIID-4379 > URL: https://issues.jboss.org/browse/TEIID-4379 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.1, 8.12.x-6.4 > > > The logic to detect duplicate entities in the simple case of no duplicates causes each entity row to be created twice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4379) OData entity row created twice

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4379?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4379: ---------------------------------- Fix Version/s: 8.12.x-6.4 > OData entity row created twice > ------------------------------ > > Key: TEIID-4379 > URL: https://issues.jboss.org/browse/TEIID-4379 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.1, 8.12.x-6.4 > > > The logic to detect duplicate entities in the simple case of no duplicates causes each entity row to be created twice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4379) OData entity row created twice

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4379?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4379. ----------------------------------- Resolution: Done > OData entity row created twice > ------------------------------ > > Key: TEIID-4379 > URL: https://issues.jboss.org/browse/TEIID-4379 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12.x-6.4, 9.1 > > > The logic to detect duplicate entities in the simple case of no duplicates causes each entity row to be created twice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4382) array_agg does not properly handle array values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4382?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4382: ---------------------------------- Fix Version/s: 8.12.x-6.4 > array_agg does not properly handle array values > ----------------------------------------------- > > Key: TEIID-4382 > URL: https://issues.jboss.org/browse/TEIID-4382 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.x-6.4 > > > array_agg(array value) - will fail to create the expected multi-dimensional array value as the ArrayAgg logic does not properly unnest the ArrayImpl values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4269) numeric calculated fields not displayed with odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4269?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4269: ---------------------------------- Fix Version/s: 8.12.x-6.4 > numeric calculated fields not displayed with odata4 > --------------------------------------------------- > > Key: TEIID-4269 > URL: https://issues.jboss.org/browse/TEIID-4269 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Mirco Marchitiello > Assignee: Ramesh Reddy > Fix For: 9.1, 8.12.x-6.4 > > > I've created a virtual table with a new field defined in this way: > select ROUND((BA.PREIS / BA.PEINH), 3) AS UnitPrice from xxxxxx > for the source field are bigdecimal I define UnitPrice as > BigDecimal (13,3) > If I run the qery from JDBC > select * from PurchaseRequisitionEntity where PurchaseRequisitionKey = '300-8000001452-00010' ; > PREIS = 539,568 > PEINH = 106 > UnitPrice = 5,090.264 > And the result is correct. If I run from odata2 > /odata/CASALE.1/Entities.PurchaseRequisitionEntity('300-8000001452-00010')?$format=json > "UnitPrice" : "5090.2640000000000000" > As you can see the field is rounded to the 3rd digit but 13 more digits are returned with 0 value. > Anyway odata2 succeeds in returning the result without errors. > With odata4 I get an error: > /odata4/CASALE.1/Entities/PurchaseRequisitionEntity('300-8000001452-00010')?$format=json > {"error":{"code":null,"message":"The value '5090.2640000000000000' is not valid for property 'UnitPrice'."}} > I think that's because the length of the field is greater then the matedata definition. > At the moment the only solution I can imagine is to convert the number to a string in the proper format and the parse it into a number -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4380) ODatat 4 deep insert works for only a single expand level

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4380?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4380: ---------------------------------- Fix Version/s: 8.12.x-6.4 > ODatat 4 deep insert works for only a single expand level > --------------------------------------------------------- > > Key: TEIID-4380 > URL: https://issues.jboss.org/browse/TEIID-4380 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.x-6.4 > > > Inserting an entity with a graph more complicated than a single expand won't work as expected - in most cases an exception will be thrown after the inserts are performed / committed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4381) OData expand with count and top=0 returns all children

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4381?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4381: ---------------------------------- Fix Version/s: 8.12.x-6.4 > OData expand with count and top=0 returns all children > ------------------------------------------------------ > > Key: TEIID-4381 > URL: https://issues.jboss.org/browse/TEIID-4381 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.1, 8.12.x-6.4 > > > If expand contains both $count=true and $top=0, all of the children be returned. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2017