June 2015 - teiid-issues - Jboss List Archives

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

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Bram Gadeyne commented on TEIID-3511: ------------------------------------- Sorry for the late reply. I'm sorry but I can not give you the data because it is medical data. I tried to reproduce this with less joins but then everything seems to work out fine. Do you have any idea what might have caused this? I now also used a temp table joined with 2 tables and then a where clause that has an exists condition with and without a BITAND function call. select * from #tmp_res gd join prod_P_Pharmas ps on ps.PatientID = gd.PatientID join prod_S_PharmaRef pr on pr.PharmaID = ps.PharmaID and pr.GenericName = 'vancomycine hydrochloride' where exists( select 1 from prod_P_PharmaRec pr where pr.OrderNumber = ps.OrderNumber and pr.PharmaID = ps.PharmaID and BITAND(pr.Status, 2) <> 2 ); > 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-3544) teiid-odata-*.war not deploying in EAP when using domain

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3544. --------------------------------- Fix Version/s: 8.7.1.6_2 Resolution: Done Added the necessary changes to deploy the odata war file from cli scripts > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3548: ------------------------------------- ofcourse, duh. I believe there were multiple build methods for this purpose. > 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.11, 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-3548) Creation of embedded complex not supported by odata production

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3548: --------------------------------------- That buildMetadata call is only called by test code, and the scenario you are describing would only happen if the association crossed schemas - which is not currently expected by any of the other logic / buildMetadata methods. > 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.11, 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-3548) Creation of embedded complex not supported by odata production

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3548: ------------------------------------- So, you went back to original commit right? only thing I saw is in "ODataEntitySchemaBuilder" you made entitytypes, functionimport, associations build in one pass of the schema. I think, I put in different for loops because, I could not build the associations until I have all the entity types in edmSchema object. > 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.11, 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-3548) Creation of embedded complex not supported by odata production

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3548: ---------------------------------- Fix Version/s: 8.11 > 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.11, 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-3548) Creation of embedded complex not supported by odata production

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3548: --------------------------------------- https://github.com/teiid/teiid/commit/a6ab738b11dbbe03f5a517df0da35634085... shows most of the fix if we want to go that route. For now went with a fix that will not build the complex type info for production. > 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.11, 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-3548) Creation of embedded complex not supported by odata production

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3548. ----------------------------------- Resolution: Done > 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.11, 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-3548) Creation of embedded complex not supported by odata production

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3548: --------------------------------------- I'm fine with that too. We just need to document or fix the exception if complextype/columngroup are used. > 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-3548) Creation of embedded complex not supported by odata production

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3548: ----------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) In light of your comments should we keep as is? Not sure how much benefit this gives other than it mimics the imported $metadata if model imported from OData service. In much larger picture, we have different properties in JPA and MongoDB in similar places. Another idea is defining the tables without PK or Unique keys as complex types, so that we do not omit them as we do currently. > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015