[
https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5394:
---------------------------------------
The limitations will be:
- only for xml based vdbs (ddl with the current restrictions is potentially supportable)
- you have to create an appropriate uber config yaml for the importing vdb
- requires the use of semantic versioning
It also may need to handle the merge of vdb properties.
It may also need to do more accounting with regards to what is an imported model. If you
for example have a grant all in an imported vdb, the current server logic only lets that
apply to the models from the imported vdb.
Having a child vdb with imports wouldn't be an issue correct? Because the artifact
built for that would itself be the merged version, which could then be remerged.
Define how to utilize multiple vdbs
-----------------------------------
Key: TEIID-5394
URL:
https://issues.jboss.org/browse/TEIID-5394
Project: Teiid
Issue Type: Sub-task
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.2
Perhaps to support vdb imports, we should define how a build can incorporate multiple
vdbs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)