November 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ] Matej Kralik commented on TEIIDDES-3117: ---------------------------------------- [~blafond] Yes it is but when the jar was only deployed by user on a server the property should be *deployment.<jar name>.jar* because EAP automatically creates a dynamic module with this [pattern name|https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Appli...]. However, when the jar is on a server as a module which user define before then the property should be *<modul name>*. Correct me If I don't understand it correctly. So I think that it is user-friendly when the users can choose way how they work with jar instead of manually edit generated -vdb.xml file. > Dynamic VDB is not generated properly for UDF function > ------------------------------------------------------ > > Key: TEIIDDES-3117 > URL: https://issues.jboss.org/browse/TEIIDDES-3117 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1 > Environment: Fedora 26 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.1 > > > I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error: > {code:java} > 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main > at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > ... 5 more > {code} > According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>. > The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar") > *Actual property* > {code:java} > <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/> > {code} > *Valid property* > {code:java} > <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3133) When JDG is used as a data source, there are not translator overrides to create

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-3133: ------------------------------------- Summary: When JDG is used as a data source, there are not translator overrides to create Key: TEIIDDES-3133 URL: https://issues.jboss.org/browse/TEIIDDES-3133 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 11.1.1 Reporter: Van Halbert Priority: Blocker In the process of creating the full workflow for materializating a view to a JDG 7 cache, Teiid Designer was made to also create the needed translator overrides when the VDB was created. However, when a JDG 7 cache is to be used as a data source, that translator override cannot be created when the VDB is created. It causes an exception in Teiid because it thinks the cache is for materialization (due to the override). So a change is needed, that when a JDG cache is not for materialization, but to be used as a datasource, the translator override should not be automatically created. Maybe (just a suggestion) when the source tables are created from the running of the JDG materialization process, they are flagged as matview type tables, so that when the VDB is created, it knows then to create the translator override. (otherwise it doesn't create the override). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3133) When JDG is used as a data source, there are not translator overrides to create

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3133?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-3133: ------------------------------------- Assignee: Barry LaFond > When JDG is used as a data source, there are not translator overrides to create > ------------------------------------------------------------------------------- > > Key: TEIIDDES-3133 > URL: https://issues.jboss.org/browse/TEIIDDES-3133 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.1.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > > In the process of creating the full workflow for materializating a view to a JDG 7 cache, Teiid Designer was made to also create the needed translator overrides when the VDB was created. However, when a JDG 7 cache is to be used as a data source, that translator override cannot be created when the VDB is created. It causes an exception in Teiid because it thinks the cache is for materialization (due to the override). > So a change is needed, that when a JDG cache is not for materialization, but to be used as a datasource, the translator override should not be automatically created. > Maybe (just a suggestion) when the source tables are created from the running of the JDG materialization process, they are flagged as matview type tables, so that when the VDB is created, it knows then to create the translator override. (otherwise it doesn't create the override). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3117: ---------------------------------------- [~mkralik] On further though. The generated -vdb.xml will NOT contain the jars, nor deploy the jars, so couldn't we just generate the "lib" property with "*deploy.<jar name>.jar*" on the assumption that the jars are ALREADY deployed? > Dynamic VDB is not generated properly for UDF function > ------------------------------------------------------ > > Key: TEIIDDES-3117 > URL: https://issues.jboss.org/browse/TEIIDDES-3117 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1 > Environment: Fedora 26 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.1 > > > I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error: > {code:java} > 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main > at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > ... 5 more > {code} > According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>. > The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar") > *Actual property* > {code:java} > <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/> > {code} > *Valid property* > {code:java} > <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3117: ---------------------------------------- [~mkralik] If a VDB contains a UDF jar, isn't it an expectation that the jar is deployed? and if multiple UDF jars are in a VDB, then users may want to pick/choose which UDF's should be deployed and which ones are already have modules defined/deployed? > Dynamic VDB is not generated properly for UDF function > ------------------------------------------------------ > > Key: TEIIDDES-3117 > URL: https://issues.jboss.org/browse/TEIIDDES-3117 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1 > Environment: Fedora 26 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.1 > > > I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error: > {code:java} > 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main > at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > ... 5 more > {code} > According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>. > The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar") > *Actual property* > {code:java} > <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/> > {code} > *Valid property* > {code:java} > <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3132) After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3132?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3132. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/c6f6271961dd929de... > After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-3132 > URL: https://issues.jboss.org/browse/TEIIDDES-3132 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: Screen Shot 2017-11-08 at 12.34.53.png > > > I discovered this while verifying TEIIDDES-3098. > After you click cancel in Set Data Source JNDI name dialogue alert is displayed, but this alert has no message set. See screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3132) After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3132?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3132: -------------------------------------- Assignee: Barry LaFond > After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-3132 > URL: https://issues.jboss.org/browse/TEIIDDES-3132 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: Screen Shot 2017-11-08 at 12.34.53.png > > > I discovered this while verifying TEIIDDES-3098. > After you click cancel in Set Data Source JNDI name dialogue alert is displayed, but this alert has no message set. See screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3132) After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3132?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3132: ----------------------------------- Fix Version/s: 11.1.1 > After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-3132 > URL: https://issues.jboss.org/browse/TEIIDDES-3132 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: Screen Shot 2017-11-08 at 12.34.53.png > > > I discovered this while verifying TEIIDDES-3098. > After you click cancel in Set Data Source JNDI name dialogue alert is displayed, but this alert has no message set. See screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-3117: ------------------------------------ > Dynamic VDB is not generated properly for UDF function > ------------------------------------------------------ > > Key: TEIIDDES-3117 > URL: https://issues.jboss.org/browse/TEIIDDES-3117 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1 > Environment: Fedora 26 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.1 > > > I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error: > {code:java} > 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main > at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1] > ... 5 more > {code} > According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>. > The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar") > *Actual property* > {code:java} > <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/> > {code} > *Valid property* > {code:java} > <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3132) After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-3132: -------------------------------------- Summary: After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed Key: TEIIDDES-3132 URL: https://issues.jboss.org/browse/TEIIDDES-3132 Project: Teiid Designer Issue Type: Bug Affects Versions: 11.1.1 Reporter: Matus Makovy Attachments: Screen Shot 2017-11-08 at 12.34.53.png I discovered this while verifying TEIIDDES-3098. After you click cancel in Set Data Source JNDI name dialogue alert is displayed, but this alert has no message set. See screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2017