November 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2725) Transformation sql is not correct when using REST import with URL attributes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2725?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2725: ----------------------------------- Fix Version/s: 9.3 > Transformation sql is not correct when using REST import with URL attributes > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2725 > URL: https://issues.jboss.org/browse/TEIIDDES-2725 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Fix For: 9.3 > > Attachments: Screen Shot 2015-11-12 at 14.55.52.png, Screen Shot 2015-11-12 at 15.22.59.png > > > When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. > ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* > SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug Description, not in screenshot) > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2725) Transformation sql is not correct when using REST import with URL attributes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2725?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2725: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1281439 Bugzilla Update: Perform > Transformation sql is not correct when using REST import with URL attributes > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2725 > URL: https://issues.jboss.org/browse/TEIIDDES-2725 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Attachments: Screen Shot 2015-11-12 at 14.55.52.png, Screen Shot 2015-11-12 at 15.22.59.png > > > When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. > ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* > SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug Description, not in screenshot) > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2725) Transformation sql is not correct when using REST import with URL attributes

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2725?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2725: ----------------------------------- Description: When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug Description, not in screenshot) See attached screenshots was: When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* SQL without the bold/underlined parts works. See attached screenshots > Transformation sql is not correct when using REST import with URL attributes > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2725 > URL: https://issues.jboss.org/browse/TEIIDDES-2725 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Attachments: Screen Shot 2015-11-12 at 14.55.52.png, Screen Shot 2015-11-12 at 15.22.59.png > > > When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. > ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* > SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug Description, not in screenshot) > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2725) Transformation sql is not correct when using REST import with URL attributes

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-2725: -------------------------------------- Summary: Transformation sql is not correct when using REST import with URL attributes Key: TEIIDDES-2725 URL: https://issues.jboss.org/browse/TEIIDDES-2725 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 9.0.4 Reporter: Matus Makovy Attachments: Screen Shot 2015-11-12 at 14.55.52.png, Screen Shot 2015-11-12 at 15.22.59.png When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* SQL without the bold/underlined parts works. See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2414) Large transformation SQL is not exported to INDEX file.

by hisao furuichi (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2414?page=com.atlassian.jira.plu... ] hisao furuichi updated TEIIDDES-2414: ------------------------------------- > Large transformation SQL is not exported to INDEX file. > ------------------------------------------------------- > > Key: TEIIDDES-2414 > URL: https://issues.jboss.org/browse/TEIIDDES-2414 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > Assignee: Paul Richardson > Fix For: 9.3 > > Attachments: test.csv > > > A large transformation SQL of a view model is not exported to INDEX file. > I have a large transformation SQL > 8192 bytes in my view model. TDesigner fails to convert the xmi to XXXXXXXXXX.INDEX file. There is no transformation SQL in the INDEX file, therefore, deploying my vdb fails and the vdb is inactivated. When you deploy the vdb, you can see the following message in a log file:- > {code} > 17:16:11,632 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31079 View ViewModel.new_table is not defined by a query expression. > 17:16:11,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata for the VDB test.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 17:16:11,637 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB test.1 is set to FAILED > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2414) Large transformation SQL is not exported to INDEX file.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2414?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2414: ------------------------------------------ An explicit limit? Not that I'm aware of. It's quite possible that it's implicit in the code though. > Large transformation SQL is not exported to INDEX file. > ------------------------------------------------------- > > Key: TEIIDDES-2414 > URL: https://issues.jboss.org/browse/TEIIDDES-2414 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > Assignee: Paul Richardson > Fix For: 9.3 > > Attachments: test.csv > > > A large transformation SQL of a view model is not exported to INDEX file. > I have a large transformation SQL > 8192 bytes in my view model. TDesigner fails to convert the xmi to XXXXXXXXXX.INDEX file. There is no transformation SQL in the INDEX file, therefore, deploying my vdb fails and the vdb is inactivated. When you deploy the vdb, you can see the following message in a log file:- > {code} > 17:16:11,632 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31079 View ViewModel.new_table is not defined by a query expression. > 17:16:11,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata for the VDB test.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 17:16:11,637 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB test.1 is set to FAILED > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2414) Large transformation SQL is not exported to INDEX file.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2414?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2414: ---------------------------------------- [~shawkins] Is there a limit on the Teiid side for BLOCK_SIZE > 8192? > Large transformation SQL is not exported to INDEX file. > ------------------------------------------------------- > > Key: TEIIDDES-2414 > URL: https://issues.jboss.org/browse/TEIIDDES-2414 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > Assignee: Paul Richardson > Fix For: 9.3 > > Attachments: test.csv > > > A large transformation SQL of a view model is not exported to INDEX file. > I have a large transformation SQL > 8192 bytes in my view model. TDesigner fails to convert the xmi to XXXXXXXXXX.INDEX file. There is no transformation SQL in the INDEX file, therefore, deploying my vdb fails and the vdb is inactivated. When you deploy the vdb, you can see the following message in a log file:- > {code} > 17:16:11,632 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31079 View ViewModel.new_table is not defined by a query expression. > 17:16:11,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata for the VDB test.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 17:16:11,637 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB test.1 is set to FAILED > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2722?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2722: ----------------------------------- Fix Version/s: 10.0 > 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 > Fix For: 10.0 > > 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-2722) User Defined properties are exported in each model in Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2722?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2722: -------------------------------------- Assignee: Barry LaFond > 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 > Assignee: Barry LaFond > Priority: Minor > Fix For: 10.0 > > 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-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 commented on TEIIDDES-2724: ---------------------------------------- *Note* this will involve ModeShape DDL parser changes as well as TeiidSequencer/TeiidParser fixes > [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 > > 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)

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