August 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2552?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2552: ---------------------------------------- [~asmigala] Since the functionality exists to re-order the parameters correctly, recommend that we consider this JIRA resolved and log an enhancement to cover the additional/changed behavior? > REST connection profile wizard creates URL with parameters in wrong order > ------------------------------------------------------------------------- > > Key: TEIIDDES-2552 > URL: https://issues.jboss.org/browse/TEIIDDES-2552 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 > Reporter: Andrej Šmigala > Assignee: Ted Jones > Priority: Critical > Fix For: 9.0.3, 9.2 > > Attachments: Newconnectionprofile_001.png > > > When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. > The URI parameters should always be added to the URL before the Query parameters. -- 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 resolved TEIIDDES-2592. ------------------------------------ Resolution: Done > 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.2, 9.0.3 > > 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-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 edited comment on TEIIDDES-2592 at 8/4/15 2:23 PM: ---------------------------------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/0832d3ebb6b38c062... 9.0.x https://github.com/Teiid-Designer/teiid-designer/commit/e3ee5cc3a51e5c499... was (Author: blafond): 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

[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 edited comment on TEIIDDES-2592 at 8/4/15 2:23 PM: ---------------------------------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/181ba01e143ba878c... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/cba3a2219aa68bded... was (Author: blafond): master: https://github.com/Teiid-Designer/teiid-designer/commit/181ba01e143ba878c... > 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 Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2460. ------------------------------------ Resolution: Done > 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.2, 9.0.3 > > 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 Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2460: ---------------------------------------- * master: https://github.com/Teiid-Designer/teiid-designer/commit/5177c33e77d63a45c... https://github.com/Teiid-Designer/teiid-designer/commit/03f3e12ea9cf94a34... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/450348a71005b797d... https://github.com/Teiid-Designer/teiid-designer/commit/bdf4791e01069b0d5... > 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-2523) Add or Remove input variables for WS operation not working correctly

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2523?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2523: ---------------------------------------- [~asmigala] Could you document how this WS was actually created? Some of the issues are a result of 2 different methods for creating the DECLARE statements. In one case, it ends up removing the fully qualified path and it's getting out of sync with the method in Add/Remove > Add or Remove input variables for WS operation not working correctly > -------------------------------------------------------------------- > > Key: TEIIDDES-2523 > URL: https://issues.jboss.org/browse/TEIIDDES-2523 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Web Services Support > Affects Versions: 8.3.4, 9.0.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Minor > Fix For: 9.0.3, 9.2 > > Attachments: WsVariablesProject.zip, WsVariablesProject_Fixed.zip > > > The variables are now shown after opening the model, however, clicking Add or Remove variables shows the Edit Input Variables editor with all the variables deselected. Selecting some of the variables adds them to the transformation, resulting in invalid SQL. > New steps to reproduce: > import the attached project > double click the OrderCheckingWs in model explorer, the model editor will open > click Add or Remove variables > notice all variables are deselected > select OrderDate, click OK > save the model, the following validation error is shown: > ERROR: Variable VARIABLES.IN_OrderDate was previously declared. > Note that as a user checks/unchecks variables, the SQL transformation is trying to keep pace with the selections and isn't staying in sync. You can end up with multiple/duplicates. Expanding the tree shows that 2 of the 3 variables show as checked. But OrderDate is Not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2523) Add or Remove input variables for WS operation not working correctly

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2523?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2523: ----------------------------------- Attachment: WsVariablesProject_Fixed.zip > Add or Remove input variables for WS operation not working correctly > -------------------------------------------------------------------- > > Key: TEIIDDES-2523 > URL: https://issues.jboss.org/browse/TEIIDDES-2523 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Web Services Support > Affects Versions: 8.3.4, 9.0.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Minor > Fix For: 9.0.3, 9.2 > > Attachments: WsVariablesProject.zip, WsVariablesProject_Fixed.zip > > > The variables are now shown after opening the model, however, clicking Add or Remove variables shows the Edit Input Variables editor with all the variables deselected. Selecting some of the variables adds them to the transformation, resulting in invalid SQL. > New steps to reproduce: > import the attached project > double click the OrderCheckingWs in model explorer, the model editor will open > click Add or Remove variables > notice all variables are deselected > select OrderDate, click OK > save the model, the following validation error is shown: > ERROR: Variable VARIABLES.IN_OrderDate was previously declared. > Note that as a user checks/unchecks variables, the SQL transformation is trying to keep pace with the selections and isn't staying in sync. You can end up with multiple/duplicates. Expanding the tree shows that 2 of the 3 variables show as checked. But OrderDate is Not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1386) Cannot multi-select schema contents when building response procedure result set (Web Service as input)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1386?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1386: ---------------------------------------- Enabling for multi-selection will be too much work at this late of date for 9.0.3. Pushing to 9.0.4. Note that double-clicking each element is still a valid option, rather than using selection + ADD button > Cannot multi-select schema contents when building response procedure result set (Web Service as input) > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1386 > URL: https://issues.jboss.org/browse/TEIIDDES-1386 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > Attachments: CannotMultiSelect.png > > > When modeling the response result set for an incoming Web Service, the user must select each attribute individually and click the Add button. Intuitively, I tried to multi-select the attributes, but that is not permitted. It should be. :-) Screenshot is attached. > I used the Oorsprong FullCountryInfo operation which has several output attributes from which to choose. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1386) Cannot multi-select schema contents when building response procedure result set (Web Service as input)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1386?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1386: ----------------------------------- Fix Version/s: 9.0.4 (was: 9.0.3) > Cannot multi-select schema contents when building response procedure result set (Web Service as input) > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1386 > URL: https://issues.jboss.org/browse/TEIIDDES-1386 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > Attachments: CannotMultiSelect.png > > > When modeling the response result set for an incoming Web Service, the user must select each attribute individually and click the Add button. Intuitively, I tried to multi-select the attributes, but that is not permitted. It should be. :-) Screenshot is attached. > I used the Oorsprong FullCountryInfo operation which has several output attributes from which to choose. -- 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