January 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2435) [Usability] The default user when connecting to server should be blanked out

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2435?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2435. ------------------------------------ Assignee: Barry LaFond (was: Paul Richardson) Resolution: Done master : https://github.com/Teiid-Designer/teiid-designer/commit/787ba98ad7a9e5c9d... > [Usability] The default user when connecting to server should be blanked out > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2435 > URL: https://issues.jboss.org/browse/TEIIDDES-2435 > Project: Teiid Designer > Issue Type: Enhancement > Components: Patch Release, Teiid Integration > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.2.1 > > > In old versions of the Teiid server, the username "user" was the default. However, with newer versions, there is no default installed user. The person installing has to set that username. Therefore, its requested that the username in Teiid Designer be blanked our so that it eliminates confusion with prior versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2731) VDB exported to Dynamic VDB XML, the foreign key relations have erroneous references in the resulting SQL.

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2731?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2731. ---------------------------------- > VDB exported to Dynamic VDB XML, the foreign key relations have erroneous references in the resulting SQL. > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2731 > URL: https://issues.jboss.org/browse/TEIIDDES-2731 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > Attachments: TestcaseforExport.zip > > > Model: > • Catalog (ID, SecondID, ThirdID). Primary key: (ID). Unique constraint: (SecondID, ThirdID) > • CatalogItem(ID,CatalogID, CatalogSecondID, CatalogThirdID) > Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > Expected in metadata DLL for CatalogItem: > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID) > Actual: > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(ID) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2731) VDB exported to Dynamic VDB XML, the foreign key relations have erroneous references in the resulting SQL.

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2731?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2731: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.5 (was: ) > VDB exported to Dynamic VDB XML, the foreign key relations have erroneous references in the resulting SQL. > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2731 > URL: https://issues.jboss.org/browse/TEIIDDES-2731 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > Attachments: TestcaseforExport.zip > > > Model: > • Catalog (ID, SecondID, ThirdID). Primary key: (ID). Unique constraint: (SecondID, ThirdID) > • CatalogItem(ID,CatalogID, CatalogSecondID, CatalogThirdID) > Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > Expected in metadata DLL for CatalogItem: > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID) > Actual: > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(ID) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2732) Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2732?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2732. ---------------------------------- > Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2732 > URL: https://issues.jboss.org/browse/TEIIDDES-2732 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > Attachments: TestcaseforImport-vdb.xml, TestcaseforImport.zip > > > AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS POINTS TO WRONG COLUMNS IN SOURCE MODEL > Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > XML INPUT fragment for Source model, table CatalogItem: > CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID), > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID) > Expected in Teiid: > CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > Actual: > CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(ID) > 3. AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS IS MISSING IN VIEW MODEL. > Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > XML INPUT fragment for View model, table CatalogItem: > CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID), > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID) > Expected in Teiid: > CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > Actual: > Not Foreign key reference at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2732) Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2732?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2732: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.5 (was: ) > Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2732 > URL: https://issues.jboss.org/browse/TEIIDDES-2732 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > Attachments: TestcaseforImport-vdb.xml, TestcaseforImport.zip > > > AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS POINTS TO WRONG COLUMNS IN SOURCE MODEL > Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > XML INPUT fragment for Source model, table CatalogItem: > CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID), > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID) > Expected in Teiid: > CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > Actual: > CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(ID) > 3. AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS IS MISSING IN VIEW MODEL. > Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > XML INPUT fragment for View model, table CatalogItem: > CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID), > CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID) > Expected in Teiid: > CatalogItem(CatalogSecondID, CatalogThirdID)  Catalog(SecondID, ThirdID) > Actual: > Not Foreign key reference at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ] Matus Makovy reopened TEIIDDES-2748: ------------------------------------ > ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2748 > URL: https://issues.jboss.org/browse/TEIIDDES-2748 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: 9.0.5, 9.2.1 > > > Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected. > On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked. > On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation> > The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2737) Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2737?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2737: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.5 (was: ) > Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2737 > URL: https://issues.jboss.org/browse/TEIIDDES-2737 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > Attachments: Testcase-integer-vdb.xml > > > Import vdb-xml into teiid-vdb: attribute with integer type gets converted into biginteger type, expected integer type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2737) Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2737?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2737. ---------------------------------- > Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2737 > URL: https://issues.jboss.org/browse/TEIIDDES-2737 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > Attachments: Testcase-integer-vdb.xml > > > Import vdb-xml into teiid-vdb: attribute with integer type gets converted into biginteger type, expected integer type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2746) Dynamic VDB export and import set bigdecimal precision to 20 if not defined and should be 0

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2746?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2746. ---------------------------------- > Dynamic VDB export and import set bigdecimal precision to 20 if not defined and should be 0 > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2746 > URL: https://issues.jboss.org/browse/TEIIDDES-2746 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > > Import vdb-xml into Teiid vdb: attribute with bigdecimal type (without precision) gets converted into bigdecimal(20) type (with precision=20), expected bigdecimal type > and > Export teiid-vdb to vdb-xml: attribute with bigdecimal type (without precision) gets converted into bigdecimal(20) type (with precision=20), expected bigdecimal type > If no precision is specified default to 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2746) Dynamic VDB export and import set bigdecimal precision to 20 if not defined and should be 0

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2746?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2746: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.5 (was: ) > Dynamic VDB export and import set bigdecimal precision to 20 if not defined and should be 0 > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2746 > URL: https://issues.jboss.org/browse/TEIIDDES-2746 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > > Import vdb-xml into Teiid vdb: attribute with bigdecimal type (without precision) gets converted into bigdecimal(20) type (with precision=20), expected bigdecimal type > and > Export teiid-vdb to vdb-xml: attribute with bigdecimal type (without precision) gets converted into bigdecimal(20) type (with precision=20), expected bigdecimal type > If no precision is specified default to 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2016