Description of problem: When I try to deploy a VDB containing a relational UDF function model, I get an error saying "One or more models in VDB are either missing a translator name or have a translator name that is not found on the current Teiid instance." The translator name for the function model is empty; but the translator names for the other source models contained in the VDB are non-empty and do exist on the server. Version-Release number of selected component (if applicable): DV 6.0.0 ER4 JBDS 7.1.0 CR1 JBIS 4.1.3 Beta5 Teiid Designer 8.3.0 CR1 OS X 10.9 How reproducible: Always Steps to Reproduce (executing E2EYahooUdfTestScript): Using Teiid Designer: 1. Select VDB containing UDF source model 2. Right-click > Modeling > Deploy Actual results: "VDB Not Deployed" error dialog is displayed. Expected results: VDB is deployed Additional info: None
Created attachment 831573 [details] VDB containing relational UDF source model
Barry LaFond <blafond> made a comment on jira TEIIDDES-1970 Note that the MarketData.xmi source model does not include translator nor connection profile info, so no data source (JNDI) can be deployed/created automatically from Designer's PreviewManager.getOrCreateDataSource() method. This method is called when a VDB is deployed, including the preview vdb for the MarketData.xmi model.
Ramesh Reddy <rareddy> made a comment on jira TEIIDDES-1970 I am attaching a yahoo translator from my local build. For future references, if you want yahoo transator, build Teiid locally and it will be in "connectors/sandbox/translator-yahoo". It does not need any connector associated with it, just like "loopback"
Ramesh Reddy <rareddy> made a comment on jira TEIIDDES-1970 Yahoo Translator
Barry LaFond <blafond> updated the status of jira TEIIDDES-1970 to Resolved
Barry LaFond <blafond> made a comment on jira TEIIDDES-1970 TEIIDDES-1973 & TEIIDDES-1974 addressed some issues that were preventing the VDB from trying to be deployed through Teiid. The use-case should now include creating the UDF in a View model instead of source model there-by making this JIRA obsolete.
Barry LaFond <blafond> updated the status of jira TEIIDDES-1970 to Closed