[JBoss JIRA] (TEIIDDES-3133) When JDG is used as a data source, there are not translator overrides to create
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3133?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3133:
----------------------------------------
master: https://github.com/Teiid-Designer/teiid-designer/commit/7a09d0feb2c99aa3f...
> 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
> Fix For: 11.1.1
>
>
> 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
[JBoss JIRA] (TEIIDDES-3133) When JDG is used as a data source, there are not translator overrides to create
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3133?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3133:
-----------------------------------
Fix Version/s: 11.1.1
> 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
> Fix For: 11.1.1
>
>
> 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
[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 resolved TEIIDDES-3117.
------------------------------------
Resolution: Done
master: https://github.com/Teiid-Designer/teiid-designer/commit/a9f5875f15266c506...
> 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
>
> Attachments: udf-jars-lib-property-in-vdb-xml.png, udf-jars-lib-warning-dialog.png
>
>
> 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
[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 edited comment on TEIIDDES-3117 at 11/9/17 10:26 AM:
------------------------------------------------------------------
[~mkralik] So based on Ramesh's comment that if UDF jars exist (or any .jar) under a "lib" folder in a *.vdb, then they deploy it as a module.... and no "lib" property is required. So...
Since Save As XML creates a -vdb.xml file and will not contain the UDF jars... then I think we can assume that the UDF's contained in the *.vdb will have to be deployed for the -vdb.xml to work. So I'll just add the *lib* property containing a comma separated list of *deployment.myUdfClasses.jar* names. I already pop up a *warning* dialog stating that UDf jars are in the *.vdb and that the XML version assumes the modules are already deployed.
See attached screenshots
Thx
was (Author: blafond):
[~mkralik] So based on Ramesh's comment that if UDF jars exist (or any .jar) under a "lib" folder in a *.vdb, then they deploy it as a module.... and no "lib" property is required. So...
Since Save As XML creates a -vdb.xml file and will not contain the UDF jars... then I think we can assume that the UDF's contained in the *.vdb will have to be deployed for the -vdb.xml to work. So I'll just add the *lib* property containing a comma separated list of *deployment.myUdfClasses.jar* names. I already pop up a *warning* dialog stating that UDf jars are in the *.vdb and that the XML version assumes the modules are already deployed.
Thx
> 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
>
> Attachments: udf-jars-lib-property-in-vdb-xml.png, udf-jars-lib-warning-dialog.png
>
>
> 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
[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 updated TEIIDDES-3117:
-----------------------------------
Attachment: udf-jars-lib-property-in-vdb-xml.png
udf-jars-lib-warning-dialog.png
> 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
>
> Attachments: udf-jars-lib-property-in-vdb-xml.png, udf-jars-lib-warning-dialog.png
>
>
> 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
[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] So based on Ramesh's comment that if UDF jars exist (or any .jar) under a "lib" folder in a *.vdb, then they deploy it as a module.... and no "lib" property is required. So...
Since Save As XML creates a -vdb.xml file and will not contain the UDF jars... then I think we can assume that the UDF's contained in the *.vdb will have to be deployed for the -vdb.xml to work. So I'll just add the *lib* property containing a comma separated list of *deployment.myUdfClasses.jar* names. I already pop up a *warning* dialog stating that UDf jars are in the *.vdb and that the XML version assumes the modules are already deployed.
Thx
> 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