February 2016 - teiid-designer-issues

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

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2414?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2414: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.0.Beta (was: ) > 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, Patch Release > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > Assignee: Paul Richardson > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > Attachments: reosurce-problem-marker.png, 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, 2 months

1
0
0 / 0

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

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2414?page=com.atlassian.jira.plu... ] Matej Kralik closed 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, Patch Release > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > Assignee: Paul Richardson > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > Attachments: reosurce-problem-marker.png, 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2771) Cannot edit Native Type extension property for procedure parameter with OUT direction

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2771?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2771: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.0.Beta (was: ) > Cannot edit Native Type extension property for procedure parameter with OUT direction > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-2771 > URL: https://issues.jboss.org/browse/TEIIDDES-2771 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Modeling > Affects Versions: 9.0.5 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 9.0.6, 10.0.1, 9.2.1 > > > Selecting an OUT parameter and editing the string ends up with empty string, so it's not getting set. > Found that RelationalModelExtensionAssistant.setPropertyValue() wasn't properly checking for NATIVE_TYPE property, so the value was never getting set. Should be simple fix. Verified that once enabled, this property is getting indexed correctly in RuntimeAdapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2771) Cannot edit Native Type extension property for procedure parameter with OUT direction

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2771?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2771. ---------------------------------- > Cannot edit Native Type extension property for procedure parameter with OUT direction > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-2771 > URL: https://issues.jboss.org/browse/TEIIDDES-2771 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Modeling > Affects Versions: 9.0.5 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 9.0.6, 10.0.1, 9.2.1 > > > Selecting an OUT parameter and editing the string ends up with empty string, so it's not getting set. > Found that RelationalModelExtensionAssistant.setPropertyValue() wasn't properly checking for NATIVE_TYPE property, so the value was never getting set. Should be simple fix. Verified that once enabled, this property is getting indexed correctly in RuntimeAdapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2783) Need to add support for parsing OPTIONS in procedure statements

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2783: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.0.Beta (was: ) > Need to add support for parsing OPTIONS in procedure statements > --------------------------------------------------------------- > > Key: TEIIDDES-2783 > URL: https://issues.jboss.org/browse/TEIIDDES-2783 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, ModeShape Integration, Patch Release > Reporter: Barry LaFond > Assignee: Dan Florian > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1 > > > The procedure DDL syntax supports OPTIONS() clause for procedure, parameter, result set, result set columns and datatype (RETURNS) clause. > CreateProcedureParser.parseReturnsClause() is not processing any OPTIONS() for procedure when RETURNS is just a datatype. See: https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... > Should be able to parse the following and set the EMF *Description* (Annotation) value when imported into Designer > {code} > CREATE FOREIGN PROCEDURE ProcedureWithRS ( > newParameter_1 string(4000) OPTIONS(ANNOTATION 'parameter 1 description'), > newParameter_2 string(4000) > ) RETURNS string(255) OPTIONS(ANNOTATION 'Example') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2783) Need to add support for parsing OPTIONS in procedure statements

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2783. ---------------------------------- > Need to add support for parsing OPTIONS in procedure statements > --------------------------------------------------------------- > > Key: TEIIDDES-2783 > URL: https://issues.jboss.org/browse/TEIIDDES-2783 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, ModeShape Integration, Patch Release > Reporter: Barry LaFond > Assignee: Dan Florian > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1 > > > The procedure DDL syntax supports OPTIONS() clause for procedure, parameter, result set, result set columns and datatype (RETURNS) clause. > CreateProcedureParser.parseReturnsClause() is not processing any OPTIONS() for procedure when RETURNS is just a datatype. See: https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... > Should be able to parse the following and set the EMF *Description* (Annotation) value when imported into Designer > {code} > CREATE FOREIGN PROCEDURE ProcedureWithRS ( > newParameter_1 string(4000) OPTIONS(ANNOTATION 'parameter 1 description'), > newParameter_2 string(4000) > ) RETURNS string(255) OPTIONS(ANNOTATION 'Example') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2796) Warning dialog when generating dynamic VDB is hardly readable

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2796: ---------------------------------------- Summary: Warning dialog when generating dynamic VDB is hardly readable Key: TEIIDDES-2796 URL: https://issues.jboss.org/browse/TEIIDDES-2796 Project: Teiid Designer Issue Type: Bug Components: Dynamic VDBs, Usability Reporter: Andrej Šmigala Priority: Minor Fix For: 10.0 Attachments: Screenshot from 2016-02-26 15-21-32.png The warning dialog that is shown when some models are omitted from a dynamic vdb has white text on gray background on linux, making the text very hard to read (see screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2758) Change interger type to biginterger/int after import

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2758?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2758: ----------------------------------- Attachment: Screen Shot 2016-02-26 at 14.37.34.png According to designer "Select a Datatype" dialogue runtime type *integer* equates to *int* at design time. So, I would suggest to convert integer to int. (or biginteger. I don't know which one corresponds to the size of old design-time type "integer" in bytes.) > Change interger type to biginterger/int after import > ---------------------------------------------------- > > Key: TEIIDDES-2758 > URL: https://issues.jboss.org/browse/TEIIDDES-2758 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Attachments: QT_MySql50_Push.vdb, Screen Shot 2016-02-26 at 14.37.34.png > > > Integer type was removed. After importing older VDB, TD complains about type incompatibility. Is there a possibility to check for integer in models after import and change it to biginterger/int? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2791) Problem with SOAP war generated in TD

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2791?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2791: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1311608|https://bugzilla.redhat.com/show_bug.cgi?id=1311608] from NEW to MODIFIED > Problem with SOAP war generated in TD > ------------------------------------- > > Key: TEIIDDES-2791 > URL: https://issues.jboss.org/browse/TEIIDDES-2791 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0 > Reporter: Matus Makovy > Priority: Critical > Attachments: ProductInfoVdb.war, Untitled.zip > > > I don't know if this is a Teiid or Teiid Designer issue. > When I generate a SOAP war from VDB and try to deploy it to server, I get following exception: > {code} > Deployment failed: ProductInfoVdb.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.deployment.unit.\"ProductInfoVdb.war\".INSTALL" : "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ProductInfoVdb.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"ProductInfoVdb.war\"\n Caused by: java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory\n Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory from [Module \"org.springframework.spring:main\" from local module loader @ed17bee (finder: local module finder @2a33fae0 (roots: /Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/dv,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/base/.overlays/layer-base-jboss-eap-6.4.3.CP,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/base))]"}}, "rolled-back" : true} > {code} > The whole "test script" should be accessible here: https://mojo.redhat.com/docs/DOC-995324 > This happens *only with DV-6.3.0.DR3*. When I deploy this war to DV 6.2 server, everything works as expected. > I attached project in zip file (Untitled.zip) and generated WAR. The WAR file was generated in TD 10.0.0.Beta2, but I tried to generate the war in 9.0.5 Designer and the result was the same. > I marked this as Critical, but if it is a Designer issue I think it should be marked as blocker. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2550) parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2550?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-2550. ---------------------------------- I have not been able reproduce this. I tried it with Teiid Designer 9.0.5.Final, 9.1.0.Final and 10.0.1 > parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2550 > URL: https://issues.jboss.org/browse/TEIIDDES-2550 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Patch Release, Transformations > Affects Versions: 9.1 > Environment: Teiid 8.7.1.redhat-8 and Teiid Designer 9.1.0.Beta1 > Reporter: Daan Creemers > Assignee: Paul Richardson > Labels: verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > Attachments: ParseTimestamp-Project.png, TestParseTimestamp.tar.gz > > > When using the parseTimestamp function in the transformation editor while creating a relational view model, a StringIndexOutOfBoundsException is thrown. The query SELECT parseTimestamp('18:10:20', 'HH:mm:ss') is used in the transformation editor which gives 'String index out of range: 1'. I want to use the function with a column of my table but produces the same error. > When deploying a virtual database and executing exactly the same query on the database, the query finishes successfully and gives the result. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2016