August 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2599) Couple issues with Teiid Connection Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2599?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2599. ------------------------------------ Resolution: Done > Couple issues with Teiid Connection Importer > -------------------------------------------- > > Key: TEIIDDES-2599 > URL: https://issues.jboss.org/browse/TEIIDDES-2599 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.2, 9.0.3 > > > If a Data Source doesn't have a driver, selecting it will cause an NPE. Need to add null check. > If a the ds name or translator type is null, then SetTranslatorPage will throw an illegal arg on widget's setText(null) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2599) Couple issues with Teiid Connection Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2599?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2599: ---------------------------------------- Added null checks master: https://github.com/Teiid-Designer/teiid-designer/commit/e2fc04e6005117bfe... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/e96c365b903d047e3... > Couple issues with Teiid Connection Importer > -------------------------------------------- > > Key: TEIIDDES-2599 > URL: https://issues.jboss.org/browse/TEIIDDES-2599 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.0.3, 9.2 > > > If a Data Source doesn't have a driver, selecting it will cause an NPE. Need to add null check. > If a the ds name or translator type is null, then SetTranslatorPage will throw an illegal arg on widget's setText(null) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2399) Creating view model from source model with generate transformations results in orphaned annotated object reference to source

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2399?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2399. ------------------------------------ Resolution: Done > Creating view model from source model with generate transformations results in orphaned annotated object reference to source > ---------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2399 > URL: https://issues.jboss.org/browse/TEIIDDES-2399 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.2, 9.0.3 > > > Create a View model from a source model and choose the "Transform.." option to generate default transformations. > The resulting View model will contain an extra <annotatedObject> reference in the same <annotations> element as the *relational* extension model reference > {code:xml} > <mmcore:AnnotationContainer xmi:uuid="mmuuid:9c7ac03c-bafc-4aa1-855f-4e6a43dd9c21"> > <annotations xmi:uuid="mmuuid:7aeb8904-fe0c-42ac-ae67-72c8ce5b397d"> > <tags xmi:uuid="mmuuid:873b6c71-41d4-476a-bf9a-442cb7fd7943" key="modelExtensionDefinition:relational" value="relational"/> > <annotatedObject href="XXXXXXX.xmi#mmuuid/7291fb4c-da39-4bbc-9787-d2edd9b9551c"/> > </annotations> > {code} > This won't cause problems for the View model, however if the View model is copied to yet another view model, the Model Import for the original source model will end up in the top level view model due to the orphaned "href=....." -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2399) Creating view model from source model with generate transformations results in orphaned annotated object reference to source

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2399?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2399: ---------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/ce9ec7715bf225348... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/f15292e4ab0c91f77... > Creating view model from source model with generate transformations results in orphaned annotated object reference to source > ---------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2399 > URL: https://issues.jboss.org/browse/TEIIDDES-2399 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.0.3, 9.2 > > > Create a View model from a source model and choose the "Transform.." option to generate default transformations. > The resulting View model will contain an extra <annotatedObject> reference in the same <annotations> element as the *relational* extension model reference > {code:xml} > <mmcore:AnnotationContainer xmi:uuid="mmuuid:9c7ac03c-bafc-4aa1-855f-4e6a43dd9c21"> > <annotations xmi:uuid="mmuuid:7aeb8904-fe0c-42ac-ae67-72c8ce5b397d"> > <tags xmi:uuid="mmuuid:873b6c71-41d4-476a-bf9a-442cb7fd7943" key="modelExtensionDefinition:relational" value="relational"/> > <annotatedObject href="XXXXXXX.xmi#mmuuid/7291fb4c-da39-4bbc-9787-d2edd9b9551c"/> > </annotations> > {code} > This won't cause problems for the View model, however if the View model is copied to yet another view model, the Model Import for the original source model will end up in the top level view model due to the orphaned "href=....." -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2460: ---------------------------------------- When Importing via teiid connection importer, the expectation is to maintain the Teiid runtime types (Teiid DDL) in Designer. The JDBC importer is JDBC metadata, so the expectation is more or less "legacy" behavior for datatype mapping. Assuming Teiid JDBC Metadata exposes the *int* version, we should be able to add a TeiidModelProcessor which can insure any *int* type stays *int*. Propose targeting 9.0.4? > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 9.0.3, 9.2 > > Attachments: ErrorDialog.png > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2592) Connecting to remote server takes a very long time

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2592?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2592: ---------------------------------------- [~asmigala] There was still an illegal arg showing up with null driver name. I fixed that as part of this jira. User can't proceed without the driver, but that's still the EPA issue. > Connecting to remote server takes a very long time > -------------------------------------------------- > > Key: TEIIDDES-2592 > URL: https://issues.jboss.org/browse/TEIIDDES-2592 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.2, 9.0.3 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.0.3, 9.2 > > Attachments: org.teiid.runtime.client.patch > > > Any interaction with remote server, such as connecting, importing from teiid connection or listing vdbs and datasources takes a very long time (minutes) when there are many datasources (30+) defined on the server > blafond: We're compiling lists of DS, Translator and VDB objects. DS's basically take 3 different CLI calls to pull together. If you're not carefull, this results in CLI calls, calling other CLI calls repeatedly > blafond: 30 Data sources were resulting in 900 + calls to the server, when it should have been maybe.... 60 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Andrej Šmigala edited comment on TEIIDDES-2460 at 8/4/15 2:59 AM: ------------------------------------------------------------------ Designer still sets the datatype to biginteger when the datatype in the deployed vdb is integer. bq. Note that Designer was changed in 9.x to not allow selecting the "integer" datatype. So the use-case was changed to define both int and string typed columns. bq. On re-import (deployed) VDB, the imported type is "integer" which is Teiid's runtime type which is supported for legacy purposes I can create a table, set the datatype to int, create and deploy vdb, import through jdbc (the imported model has the the datatype set to integer), create and deploy another vdb with the new model and import through jdbc again. The second imported model has the datatype set to biginteger. I agree this is a rather convoluted use-case, but it is not unthinkable that the user has an older vdb (created in previous versions of designer) deployed and is trying to import it. was (Author: asmigala): Designer still sets the datatype to biginteger when the datatype in the deployed vdb is integer. bq. Note that Designer was changed in 9.x to not allow selecting the "integer" datatype. So the use-case was changed to define both int and string typed columns. bq. On re-import (deployed) VDB, the imported type is "integer" which is Teiid's runtime type which is supported for legacy purposes I can create a table set the datatype to int, create and deploy vdb, import through jdbc (the imported model has the the datatype set to integer), create and deploy another vdb with the new model and import through jdbc again. The second imported model has the datatype set to biginteger. I agree this is a rather convoluted use-case, but it is not unthinkable that the user has an older vdb (created in previous versions of designer) deployed and is trying to import it. > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 9.0.3, 9.2 > > Attachments: ErrorDialog.png > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Andrej Šmigala reopened TEIIDDES-2460: -------------------------------------- Designer still sets the datatype to biginteger when the datatype in the deployed vdb is integer. bq. Note that Designer was changed in 9.x to not allow selecting the "integer" datatype. So the use-case was changed to define both int and string typed columns. bq. On re-import (deployed) VDB, the imported type is "integer" which is Teiid's runtime type which is supported for legacy purposes I can create a table set the datatype to int, create and deploy vdb, import through jdbc (the imported model has the the datatype set to integer), create and deploy another vdb with the new model and import through jdbc again. The second imported model has the datatype set to biginteger. I agree this is a rather convoluted use-case, but it is not unthinkable that the user has an older vdb (created in previous versions of designer) deployed and is trying to import it. > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 9.0.3, 9.2 > > Attachments: ErrorDialog.png > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2600) DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2600: -------------------------------------- Summary: DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE Key: TEIIDDES-2600 URL: https://issues.jboss.org/browse/TEIIDDES-2600 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Barry LaFond Fix For: 9.2, 9.0.4 Trying to import the following DDL into a View model (see: TEIIDDES-1794) the resulting Table has the Global Temp Table value set to *false*. I don't think the TeiidDdlImporter is handling these particular cases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2592) Connecting to remote server takes a very long time

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2592?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2592: ---------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/0832d3ebb6b38c062... > Connecting to remote server takes a very long time > -------------------------------------------------- > > Key: TEIIDDES-2592 > URL: https://issues.jboss.org/browse/TEIIDDES-2592 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.2, 9.0.3 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.0.3, 9.2 > > Attachments: org.teiid.runtime.client.patch > > > Any interaction with remote server, such as connecting, importing from teiid connection or listing vdbs and datasources takes a very long time (minutes) when there are many datasources (30+) defined on the server > blafond: We're compiling lists of DS, Translator and VDB objects. DS's basically take 3 different CLI calls to pull together. If you're not carefull, this results in CLI calls, calling other CLI calls repeatedly > blafond: 30 Data sources were resulting in 900 + calls to the server, when it should have been maybe.... 60 -- 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-designer-issues August 2015