June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3548) Creation of embedded complex not supported by odata production

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3548: ------------------------------------- Summary: Creation of embedded complex not supported by odata production Key: TEIID-3548 URL: https://issues.jboss.org/browse/TEIID-3548 Project: Teiid Issue Type: Bug Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 Prior to 8.11 we would always produce the flattened version with or without the complex type extension metadata. With TEIID-3543 the extension metadata will cause production to throw an exception. The workaround until this is fixed is to not use the complex type extension metadata. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3511: ---------------------------------- Fix Version/s: 8.12 > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 8.12 > > Attachments: debugplan_bitand.txt, debugplan_bitand_correct.txt, debugplan_nobitand.txt, debugplan_nobitand_correct.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3543: --------------------------------------- >From what I can tell it's pretty involved to add complex type support to the production side. I vote for logging a new issue and putting it into 8.12 > Complex type values not resolved in translator execution > -------------------------------------------------------- > > Key: TEIID-3543 > URL: https://issues.jboss.org/browse/TEIID-3543 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: > {code} > java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails > at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3543: --------------------------------------- > This also raises the question of whether we need to move some of the extension metadata from translator specific to engine level to give freedom to the user how they define OData metadata. I think we're fine. If they want the old behavior (just a flat service exposed), then they shouldn't use the complextype and columngroup extension metadata. We just need to fix the creation of nested complex types when the extension metadata is present. > Complex type values not resolved in translator execution > -------------------------------------------------------- > > Key: TEIID-3543 > URL: https://issues.jboss.org/browse/TEIID-3543 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: > {code} > java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails > at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3543: --------------------------------------- Correction we'll throw an exception. > Complex type values not resolved in translator execution > -------------------------------------------------------- > > Key: TEIID-3543 > URL: https://issues.jboss.org/browse/TEIID-3543 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: > {code} > java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails > at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3543: ------------------------------------- Yes, previously we would have been showing the entity type with complex type folded in, this will change that. The whole issue arises from using the same EDM parsing module for translator and on out OData service. Translator EDM parser should be exactly same as what source represents. The outbound one is our interpretation of Teiid schema to OData schema. This was bad choice on my part, which I did not foresee before. This also raises the question of whether we need to move some of the extension metadata from translator specific to engine level to give freedom to the user how they define OData metadata. For now we need to test complex property navigation is still works with V2. > Complex type values not resolved in translator execution > -------------------------------------------------------- > > Key: TEIID-3543 > URL: https://issues.jboss.org/browse/TEIID-3543 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: > {code} > java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails > at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3543: --------------------------------------- >From what I can tell, that will need another issue. With the updated metadata we still don't create the nested entries, just a flat set of properties. > Complex type values not resolved in translator execution > -------------------------------------------------------- > > Key: TEIID-3543 > URL: https://issues.jboss.org/browse/TEIID-3543 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: > {code} > java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails > at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3543: --------------------------------------- This and TEIID-3538 are on both branches. By outbound you mean our generated odata service? We need to add a test for that as well. > Complex type values not resolved in translator execution > -------------------------------------------------------- > > Key: TEIID-3543 > URL: https://issues.jboss.org/browse/TEIID-3543 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: > {code} > java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails > at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3543: ------------------------------------- After looking at commit, actually this also fixes the unflattering effect on EntityTypes in outbound OData service. There are will be no changes to V4 as there no translator yet for V4. > Complex type values not resolved in translator execution > -------------------------------------------------------- > > Key: TEIID-3543 > URL: https://issues.jboss.org/browse/TEIID-3543 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: > {code} > java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails > at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3538) Make OData V2 compatible with LINQPad

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3538?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3538: ------------------------------------- Also good candidate for 6.2, need to still test using Visual Studio for V4 > Make OData V2 compatible with LINQPad > ------------------------------------- > > Key: TEIID-3538 > URL: https://issues.jboss.org/browse/TEIID-3538 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.11 > > > Current OData V2 implementation is not able to load in LINQPad https://www.linqpad.net/ > Couple issues found > - List(Edm.xxx) based collections are not supported. V2 Spec did not specify any List based collections. Only Collection(Edm.xxx) type. So, part of TEIID-3471 need to be rolled back and fix with Collection(Edm.xxx) type > - Explicit definition of "not null" in Entity's key property. > - TEIID-3471 did not go far enough to define accepts header to have "application/xml", "application/atom+xml" and "application/json" without "chaset=utf-8" appended to it. TEIID-3471 only added $metadata and service document. BTW, I was under the impression that I did add all the required places, and was surprised not see in commit :( -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015