November 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2722) User Defined properties are exported in each model in Dynamic VDB

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2722?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2722: ------------------------------------- Priority: Minor (was: Major) > User Defined properties are exported in each model in Dynamic VDB > ----------------------------------------------------------------- > > Key: TEIIDDES-2722 > URL: https://issues.jboss.org/browse/TEIIDDES-2722 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Priority: Minor > Attachments: CustomPropertyProject.zip > > > When exporting a VDB with user defined properties, the properties are added to each model in the resulting -vdb.xml. It would make more sense to include them once in the vdb root. > Current -vdb.xml > {code:xml} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <vdb name="CustomPropertyVdb" version="1"> > <description /> > <property name="validationDateTime" value="Tue Nov 10 13:51:23 CET 2015" /> > <property name="validationVersion" value="8.7.1" /> > <model name="ViewModel2" type="VIRTUAL"> > <property name="lib" value="test" /> > <property name="myCustomProperty" value="someValue" /> > <metadata type="DDL"><![CDATA[ ... ]]></metadata> > </model> > <model name="ViewModel" type="VIRTUAL"> > <property name="lib" value="test" /> > <property name="myCustomProperty" value="someValue" /> > <metadata type="DDL"><![CDATA[ ... ]]></metadata> > </model> > </vdb> > {code} > Expected -vdb.xml > {code:xml} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <vdb name="CustomPropertyVdb" version="1"> > <description /> > <property name="validationDateTime" value="Tue Nov 10 13:51:23 CET 2015" /> > <property name="validationVersion" value="8.7.1" /> > <property name="lib" value="test" /> > <property name="myCustomProperty" value="someValue" /> > <model name="ViewModel2" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ ... ]]></metadata> > </model> > <model name="ViewModel" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ ... ]]></metadata> > </model> > </vdb> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2713) UDF jar not referenced in exported dynamic VDB

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2713?page=com.atlassian.jira.plu... ] Andrej Šmigala commented on TEIIDDES-2713: ------------------------------------------ This effectively prevents round-tripping the VDB import/export > UDF jar not referenced in exported dynamic VDB > ---------------------------------------------- > > Key: TEIIDDES-2713 > URL: https://issues.jboss.org/browse/TEIIDDES-2713 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Fix For: 9.3 > > > When exporting a VDB with a User Defined Function, the information about the UDF jar is not present in the resulting dynamic VDB file. > With regular VDB archives, the UDF jar is added to the lib/ directory within the archive and is referenced like so in META-INF/vdb.xml: > {code:xml} > <entry path="/lib/MyTestUdf-1.0-SNAPSHOT.jar"> > <property name="checksum" value="2689317444"/> > </entry> > {code} > This approach is not possible in case of dynamic VDB defined only as an xml file. It is, however, possible to create a module on the server with UDF jar and then reference it in the *-vdb.xml like so: > {code:xml} > <property name ="lib" value ="mytestudf-module"></property> > {code} > It is currently possible to define such property manually in the VDB editor before exporting, but Designer should be able to define one automatically, or at least warn the user when there is a UDF jar present and the lib property is not defined. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2721) message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2721?page=com.atlassian.jira.plu... ] Bram Gadeyne commented on TEIIDDES-2721: ---------------------------------------- The issue seems to be resolved after saving the VDB again with a new version number. > message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2721 > URL: https://issues.jboss.org/browse/TEIIDDES-2721 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.2 > Reporter: Bram Gadeyne > > The designer gives me this error message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." The vdb however was created in version 9.1.1. and I'm using 9.2.0. > Is there a possibility to "upgrade" a vdb to a newer version or see what is incompatible? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2721) message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer

by Bram Gadeyne (JIRA)

Bram Gadeyne created TEIIDDES-2721: -------------------------------------- Summary: message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer Key: TEIIDDES-2721 URL: https://issues.jboss.org/browse/TEIIDDES-2721 Project: Teiid Designer Issue Type: Bug Affects Versions: 9.2 Reporter: Bram Gadeyne The designer gives me this error message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." The vdb however was created in version 9.1.1. and I'm using 9.2.0. Is there a possibility to "upgrade" a vdb to a newer version or see what is incompatible? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2584) Suggestion for installation procedure teiid designer

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2584?page=com.atlassian.jira.plu... ] Bram Gadeyne commented on TEIIDDES-2584: ---------------------------------------- Hi, I've just installed version 9.2.0 of the designer in an eclipse Luna installation. I saw that the installation steps are changed a little but they indicate to install "Teiid Designer 9.2" from the last update site. However I've also installed the client and runtime libraries to make it work. Otherwise I got the same error as I mentioned as discussed in this issue. > Suggestion for installation procedure teiid designer > ---------------------------------------------------- > > Key: TEIIDDES-2584 > URL: https://issues.jboss.org/browse/TEIIDDES-2584 > Project: Teiid Designer > Issue Type: Quality Risk > Reporter: Bram Gadeyne > Attachments: eclipse.log > > > In the Download and Install page for teiiddesigner in Luna, it says Install Teiid Designer 9.1. Might I suggest to explicitly indicate to install the runtime and clients? I first installed the software without selecting these explicitly and this resulted in "implementation not found" exceptions. > > With kind regards > Bram -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2699) Issues with Dynamic VDB import/export

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2699?page=com.atlassian.jira.plu... ] Andrej Šmigala commented on TEIIDDES-2699: ------------------------------------------ [~blafond] so there is no way to export XML models as DDL? My concern here is that the original request involved round-tripping the VDBs, which would not be possible if the VDB contains XML models. > Issues with Dynamic VDB import/export > ------------------------------------- > > Key: TEIIDDES-2699 > URL: https://issues.jboss.org/browse/TEIIDDES-2699 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.3 > > > Tracking jira for all issues with dynamic VDB import and export -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

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

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2720: ---------------------------------------- Summary: 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 [~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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2699) Issues with Dynamic VDB import/export

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2699?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2699: ---------------------------------------- [~asmigala] Teiid Designer was built as a metamodeling tool and currently supports XMI (relational, web services, xml) and XSD models. Teiid Runtime continues to support those metamodels, but using their legacy VDB archive. The Dynamic VDB XML definition is really limited to Relational DDL and does not directly support Web Services and XML. WS Operations are really just Virtual Procedures, so we could convert WS models in the near term. XML Documents are treated as "Tables" at runtime and get Indexed by Designer. However, there is separate indexed metadata for XML Document models that are NOT supported by Teiid DDL. > Issues with Dynamic VDB import/export > ------------------------------------- > > Key: TEIIDDES-2699 > URL: https://issues.jboss.org/browse/TEIIDDES-2699 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.3 > > > Tracking jira for all issues with dynamic VDB import and export -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2719?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2719: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1279494 Bugzilla Update: Perform > 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 > 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)

8 years, 7 months

1
0
0 / 0

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

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2719: ---------------------------------------- Summary: 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 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)

8 years, 7 months

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