August 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2606) Procedure parameter updated even when canceling the edit dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2606?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2606: --------------------------------------------------- Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1251433|https://bugzilla.redhat.com/show_bug.cgi?id=1251433] from MODIFIED to VERIFIED > Procedure parameter updated even when canceling the edit dialog > --------------------------------------------------------------- > > Key: TEIIDDES-2606 > URL: https://issues.jboss.org/browse/TEIIDDES-2606 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 9.0.3 > Reporter: Andrej Šmigala > Priority: Minor > Labels: release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.0.3 > > > When editing parameters for a relational view procedure using the new parameter editor dialog (see TEIIDDES-2557), clicking cancel does not revert the old values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2606) Procedure parameter updated even when canceling the edit dialog

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2606?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2606: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.3.CR2 (was: ) > Procedure parameter updated even when canceling the edit dialog > --------------------------------------------------------------- > > Key: TEIIDDES-2606 > URL: https://issues.jboss.org/browse/TEIIDDES-2606 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 9.0.3 > Reporter: Andrej Šmigala > Priority: Minor > Labels: release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.0.3 > > > When editing parameters for a relational view procedure using the new parameter editor dialog (see TEIIDDES-2557), clicking cancel does not revert the old values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2606) Procedure parameter updated even when canceling the edit dialog

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2606?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2606. ---------------------------------- > Procedure parameter updated even when canceling the edit dialog > --------------------------------------------------------------- > > Key: TEIIDDES-2606 > URL: https://issues.jboss.org/browse/TEIIDDES-2606 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 9.0.3 > Reporter: Andrej Šmigala > Priority: Minor > Labels: release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.0.3 > > > When editing parameters for a relational view procedure using the new parameter editor dialog (see TEIIDDES-2557), clicking cancel does not revert the old values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2460: ------------------------------------------ > If BigInteger is the datatype, then I'm not sure we can assume it's an "int"? Generally information about the design time type is not exposed by DatabaseMetaData - only the runtime type. Our BigInteger columns would have a type code of Numeric in the DatabaseMetaData. You have to go off of the type name, the java classname, or the scale to infer that it's a biginteger column. There is nothing to indicate that the design time type is integer. So if the source vdb had design time type integer, which is the runtime type biginteger, then I don't see a problem with reimporting it as biginteger. > 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, TEIIDDES2460.zip > > > 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, 8 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: ---------------------------------------- [~asmigala] Once a VDB is deployed to a server, then Teiid loadds/creates the VDB's JDBC metadata. When Teiid exposes this JDBC metadata, I'm not sure what Designer can/should assume when it gets the metadata. If BigInteger is the datatype, then I'm not sure we can assume it's an "int"? [~shawkins] [~rareddy]] suggestions? > 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, TEIIDDES2460.zip > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2611) Resize transformation editor crash Developer Studio

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2611?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2611: ----------------------------------- Fix Version/s: 9.2 9.0.4 > Resize transformation editor crash Developer Studio > --------------------------------------------------- > > Key: TEIIDDES-2611 > URL: https://issues.jboss.org/browse/TEIIDDES-2611 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 9.0.3 > Environment: Max OS X (10.10.3) > Mac mini (Late 2012) > Reporter: Matej Kralik > Priority: Minor > Fix For: 9.2, 9.0.4 > > > When I resize transformation editor window in XML document model, developer studio crash. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 commented on TEIIDDES-2460: ------------------------------------------ [~blafond] that would not address the case when the user already has a VDB deployed on the server with the integer datatype and wants to reuse the models. > 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, TEIIDDES2460.zip > > > 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, 8 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: ---------------------------------------- [~asmigala] I propose creating another JIRA where we: * create a validation check for *integer* datatypes and create WARNING problem markers * create a Quick Fix that will change ALL *integer* datatypes to *int* User would still have to synchronize their VDB if it exists, but this would help users migrate/fix their old project set. Then this issue could be resolved/closed > 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, TEIIDDES2460.zip > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2569) Merge various fixes onto 9.0.x for 9.0.3 release

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2569?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2569. ---------------------------------- > Merge various fixes onto 9.0.x for 9.0.3 release > ------------------------------------------------ > > Key: TEIIDDES-2569 > URL: https://issues.jboss.org/browse/TEIIDDES-2569 > Project: Teiid Designer > Issue Type: Task > Components: Release Work > Affects Versions: 9.0.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2542) REST connection profile parameters settings problems (adding + deleting)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2542?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2542: --------------------------------------------------- Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1224946|https://bugzilla.redhat.com/show_bug.cgi?id=1224946] from MODIFIED to VERIFIED > REST connection profile parameters settings problems (adding + deleting) > ------------------------------------------------------------------------ > > Key: TEIIDDES-2542 > URL: https://issues.jboss.org/browse/TEIIDDES-2542 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 > Environment: MAC OS X > Reporter: Matus Makovy > Assignee: Ted Jones > Priority: Critical > Labels: release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.1, 9.0.3 > > Attachments: paramters.mov > > > There is a couple of issues with adding and deleting parameters. > See attached video. > Issue discovered on MAC OS X. > When adding parameter after changes in Type of previously added parameters the dialogue duplicates previously added parameters. > Afterwards there is problem with deleting parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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