[
https://jira.jboss.org/browse/TEIID-1182?page=com.atlassian.jira.plugin.s...
]
Barry LaFond commented on TEIID-1182:
-------------------------------------
For 7.1 Teiid Designer has elevated the Function model to a primary metamodel type and now
allows users to create multiple Function models in their workspace.
And, like any workspace, users can create folders and subfolders and place any model/file
in those folders.
If we do not choose option 3), then Teiid Designer will be required to PREVENT users from
creating/moving/refactoring Function models into any workspace location that's NOT a
Model Project.
If we choose options 1) or 2) we'll have to write custom code in VDB to set up the
folder structure (if 2)) and locate the UDF model appropriately.
Lastly, if VDB's can have only ONE UDF model, we'll also have to prevent users
from adding more than one to a VDB.
So based on what the solution is for this JIRA, please create a corresponding Designer
JIRA to cover the tooling aspects.
UDF model is not being loaded if the file is not placed in the root
location of VDB
-----------------------------------------------------------------------------------
Key: TEIID-1182
URL:
https://jira.jboss.org/browse/TEIID-1182
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Critical
Fix For: 7.1
When the "UDF" model is placed in sub-directory other than the root directory,
the VDB deployer is unable to the UDF model. The reason is VDB deployment scanner only
scans the VDB artifact in known locations of the VDB directory structure. All other
locations are ignored.
The possible solutions are
1) Place the UDF always in root location of VDB
2) Place the UDF file in a known sub-directory like "UDF"
3) Make the VDB deployer scan all the directories.
Although (3) seems to be most flexible option, I am not sure that is possible. In that
case (2) needs to be pursued, along with tooling support.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira