November 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2716) Improve importing of dynamic VDBs

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2716?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2716: ----------------------------------- Component/s: Dynamic VDBs VDB & Execution > Improve importing of dynamic VDBs > --------------------------------- > > Key: TEIIDDES-2716 > URL: https://issues.jboss.org/browse/TEIIDDES-2716 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dynamic VDBs, VDB & Execution > Reporter: Matus Makovy > Fix For: 10.1 > > > If you want to import dynamic VDB now, you have to import a file to a project and then right-click the dynamic VDB and select Modeling -> Generate VDB archive and models. > I thnik it could be more user friendly. For example there could be an option to import dynamic VDB using: File -> Import -> Dynamic VDB. One wizard would guide you through the whole import of the vdb xml file to the project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2716) Improve importing of dynamic VDBs

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2716?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2716: ----------------------------------- Fix Version/s: 10.1 > Improve importing of dynamic VDBs > --------------------------------- > > Key: TEIIDDES-2716 > URL: https://issues.jboss.org/browse/TEIIDDES-2716 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dynamic VDBs, VDB & Execution > Reporter: Matus Makovy > Fix For: 10.1 > > > If you want to import dynamic VDB now, you have to import a file to a project and then right-click the dynamic VDB and select Modeling -> Generate VDB archive and models. > I thnik it could be more user friendly. For example there could be an option to import dynamic VDB using: File -> Import -> Dynamic VDB. One wizard would guide you through the whole import of the vdb xml file to the project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2720) Convert WS models to procedures when exporting Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2720: ----------------------------------- Fix Version/s: 9.2.1 > Convert WS models to procedures when exporting Dynamic VDB > ---------------------------------------------------------- > > Key: TEIIDDES-2720 > URL: https://issues.jboss.org/browse/TEIIDDES-2720 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, VDB & Execution, Web Services Support > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Fix For: 9.2.1 > > > [~blafond]: > {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote} > Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2719) DDL for UDF in exported dynamic VDB contains RETURN parameter

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2719?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2719: ----------------------------------- Fix Version/s: 9.2.1 > DDL for UDF in exported dynamic VDB contains RETURN parameter > ------------------------------------------------------------- > > Key: TEIIDDES-2719 > URL: https://issues.jboss.org/browse/TEIIDDES-2719 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, VDB & Execution > Affects Versions: 9.2 > Reporter: Andrej Šmigala > Fix For: 9.2.1 > > Attachments: UdfProject.zip > > > When exporting VDB with a UDF, the resulting DDL contains the RETURN parameter in the parameters list. According to the [Teiid docs|https://docs.jboss.org/author/display/teiid87final/Support+for+User-...], the return parameter should not be specified. > Generated DDL: > {code:sql} > CREATE VIRTUAL FUNCTION concatNull (stringLeft string(4000), stringRight string(4000), result string(4000)) RETURNS string > ) OPTIONS("FUNCTION-CATEGORY" 'MY_TESTING_FUNCTION_CATEGORY', JAVA_CLASS 'userdefinedfunctions.MyConcatNull', JAVA_METHOD 'myConcatNull') > {code} > Expected DDL: > {code:sql} > CREATE VIRTUAL FUNCTION concatNull (stringLeft string(4000), stringRight string(4000)) RETURNS string > OPTIONS("FUNCTION-CATEGORY" 'MY_TESTING_FUNCTION_CATEGORY', JAVA_CLASS 'userdefinedfunctions.MyConcatNull', JAVA_METHOD 'myConcatNull') > {code} > (note that the generated DDL also contains an unrelated syntax error due to TEIIDDES-2697) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2720) Convert WS models to procedures when exporting Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2720: -------------------------------------- Assignee: Barry LaFond > Convert WS models to procedures when exporting Dynamic VDB > ---------------------------------------------------------- > > Key: TEIIDDES-2720 > URL: https://issues.jboss.org/browse/TEIIDDES-2720 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2.1 > > > [~blafond]: > {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote} > Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2720) Convert WS models to procedures when exporting Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2720: ----------------------------------- Component/s: Dynamic VDBs Patch Release (was: VDB & Execution) > Convert WS models to procedures when exporting Dynamic VDB > ---------------------------------------------------------- > > Key: TEIIDDES-2720 > URL: https://issues.jboss.org/browse/TEIIDDES-2720 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Fix For: 9.2.1 > > > [~blafond]: > {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote} > Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2724) [Usability] Importing DDL that has unsupported syntax is not indicated in error message

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2724?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2724: ----------------------------------- Fix Version/s: 10.1 > [Usability] Importing DDL that has unsupported syntax is not indicated in error message > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2724 > URL: https://issues.jboss.org/browse/TEIIDDES-2724 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0.3 > Reporter: Van Halbert > Fix For: 10.1 > > > Importing DDL that contains unsupported syntax produces the following "Import Messages": > - 2 instances of a DDL statement of type [ddl:ddlProblem] were found, but cannot be processed > This message doesn't give any indication as to which statement (s) are the issue. And didn't find any message(s) in the .log file either. It would be better if "ddl:ddlProblem" was replaced with the first "x" number of characters from the statement that was identified as a problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2732?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2732: ----------------------------------- Component/s: Dynamic VDBs > 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 > Fix For: 9.2.1 > > Attachments: 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)

9 years

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 Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2731?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2731: ----------------------------------- Fix Version/s: 9.2.1 > 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: Import/Export > Affects Versions: 9.2 > Reporter: Debbie Steigner > Fix For: 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)

9 years

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 Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2731?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2731: ----------------------------------- Component/s: Dynamic VDBs Patch Release > 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 > Fix For: 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)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2015