December 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3087. ------------------------------------ Resolution: Done > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.2, 11.1 > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3034) Importing Virtual Procedure DDL containing a simple RETURNS type add a Result Set to procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3034?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3034: ----------------------------------- Fix Version/s: 11.1.2 > Importing Virtual Procedure DDL containing a simple RETURNS type add a Result Set to procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3034 > URL: https://issues.jboss.org/browse/TEIIDDES-3034 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1, 11.1.1, 11.1.2 > > Attachments: viewModelFromComment.png, viewModelFromDescription.png > > > testing and debugging for TEIIDDES-2783 exposed an issue when importing a procedure containing a RETURNS data type and no result set. > The transformation resolving framework contains logic that will auto-create a result set containing a generated column. > We need to catch this use-case and prevent the result set from being created using this simple DDL input > {code} > CREATE VIRTUAL PROCEDURE ProcedureWithRS ( > stringIN string(4000) OPTIONS(ANNOTATION 'parameter 1 description') > ) RETURNS string(255) OPTIONS(ANNOTATION 'Example') AS > BEGIN > SELECT stringIN AS result; > END > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2865) JDBC importer imports MSSQL Server datatype numeric(9, [0-9]) as bigdecimal with zero precision

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2865?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2865: ----------------------------------- Fix Version/s: 11.1.2 (was: 11.1) > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2865 > URL: https://issues.jboss.org/browse/TEIIDDES-2865 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0, 9.0.5, 9.0.6, 9.0.7 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.1, 11.1.2 > > Attachments: debTest2Import.png, debtestImport.png, importedColumns.png > > > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision and should be 9. I believe this https://issues.jboss.org/browse/TEIIDDES-2746 may have changed the behavior, in version 9.0.3 it imports correctly. > You can use jdbc:sqlserver://ENGNTDBS14.mw.lab.eng.bos.redhat.com:1433;databaseName=mss_eds > user - mss_eds > password - mss_eds > table - debtest2, both columns are numeric(9,2) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3097: ----------------------------------- Fix Version/s: 11.1.2 > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1, 11.1.1, 11.1.2 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, webServiceJNDI.png > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3163) Translator override properties can not be updated after re-generating a dynamic vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3163?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3163: ----------------------------------- Fix Version/s: 11.1.2 (was: 11.1.1) > Translator override properties can not be updated after re-generating a dynamic vdb > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-3163 > URL: https://issues.jboss.org/browse/TEIIDDES-3163 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 11.1.1 > Environment: Devstudio 11.1.0 CR1 (Teiid Desinger 11.1.1) > Reporter: Hiroki Daicho > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: reproducer_project.zip > > > If dynamic vdb has already generated, Translator override properties can not be modified by regenerate dynamic vdb. > 1. Add Translator override property to vdb (testvdb.vdb). e.g. prop1 -> 100 > 2. generate dynamic vdb (testvdb-vdb.xml). > {code} > <property name="prop1" value="100"/> > {code} > 3. Modify the propery in vdb (testvdb.vdb). e.g. prop1 -> 199 > 4. generate dynamic vdb (testvdb-vdb.xml). > 5. the property is not updated to 199 in the dynamic vdb xml. > {code} > <property name="prop1" value="100"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3087: ----------------------------------- Fix Version/s: 11.1.2 > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1, 11.1.2 > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3162) ModuleNotFoundException occurs with dynamic vdb including UDF Jars

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3162?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3162: ----------------------------------- Fix Version/s: 11.1.2 (was: 11.1.1) > ModuleNotFoundException occurs with dynamic vdb including UDF Jars > ------------------------------------------------------------------ > > Key: TEIIDDES-3162 > URL: https://issues.jboss.org/browse/TEIIDDES-3162 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 11.1.1 > Environment: DevstudioIS 11.1.0 CR1 (Teiid Desinger 11.1.1) > Reporter: Hiroki Daicho > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: reproducer_project.zip, v2_vdb.xml > > > Teiid desinger 11.1.1 generate UDF jars with comma separated to dynamic vdb as follows. > {code} > <property name="lib" value="deployement.test.jar, deployement.test2.jar"/> > {code} > But ModuleNotFoundException occurs in teiid server when the dynamic vdb deployed. > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."testvdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."testvdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "testvdb-vdb.xml" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.6.Final-redhat-1.jar:1.1.6.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.6.Final-redhat-1.jar:1.1.6.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module deployment.test.jar, for UDF in VDB testvdb.1:org.jboss.modules.ModuleNotFoundException: deployment.test.jar,:main > at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2] > ... 5 more > {code} > Teiid expects space delimited list for the module names. > "The lib property value may contain a space delimited list of module names if more than one dependency is needed." > https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtuali... > If changing vdb to use space delimited as follows, deployment was succeeded. > {code} > <property name="lib" value="deployement.test.jar deployement.test2.jar"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3165) Missing native and index metadata tag in .vdb when infinispan translator is overriding .vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3165?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3165: ----------------------------------- Fix Version/s: 11.1.2 (was: 11.1.1) > Missing native and index metadata tag in .vdb when infinispan translator is overriding .vdb > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3165 > URL: https://issues.jboss.org/browse/TEIIDDES-3165 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Assignee: Matej Kralik > Priority: Critical > Fix For: 11.1.2 > > > According to this issue [TEIIDDES-3120|https://issues.jboss.org/browse/TEIIDDES-3120] The designer adds NATIVE an INDEX metadata tags to the .vdb when a model contains infinispan-hotrod translator. However, when the translator is overriding, the metadata are not added and designer by default override infinispan translator. Probably same solution as here [TEIIDDES-3142|https://issues.jboss.org/browse/TEIIDDES-3142] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3167) Teiid Connection Import - The deployment timeout once edited will not work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3167?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3167: ----------------------------------- Fix Version/s: 11.1.2 (was: 11.1.1) > Teiid Connection Import - The deployment timeout once edited will not work > -------------------------------------------------------------------------- > > Key: TEIIDDES-3167 > URL: https://issues.jboss.org/browse/TEIIDDES-3167 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.2 > > > Using Teiid Designer 11.1 version (did not test older versions), during the import process using the Teiid Connection importer, if you change the default timeout property from 120 to any value (on the advanced tab) from there on any teiid connection importer deployments will fail with timeout. Even setting back to 120 will not work. > I feel the code somewhere may be interpreting the value as milliseconds instead of seconds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3084) Support modeling of a JDG 7.1 data source using new translator/connector

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3084?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-3084. ---------------------------------- I still see issue during Teiid importer as Van said in [comment|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13...] however the workaround exist (using JDBC importer), I create new JIRA ( [TEIIDDES-3169|https://issues.jboss.org/browse/TEIIDDES-3169] ) and closed this issue. > Support modeling of a JDG 7.1 data source using new translator/connector > ------------------------------------------------------------------------ > > Key: TEIIDDES-3084 > URL: https://issues.jboss.org/browse/TEIIDDES-3084 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes > Fix For: 11.1 > > Attachments: materialize-action.png, materialize-wizard-page-1-jdg-6.png, materialize-wizard-page-1-jdg-7.png, materialize-wizard-page-2-jdg-7.png, materialized-view-extension-props.png > > > Add the ability to model a JDG 7.1 data source using new Teiid connector/translator -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2017