[
https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1366:
---------------------------------------
In option (1) since the merging only happens at deployment time, the deployment of a new
dependent version would not get picked up until a server restart or redeployment of parent
vdbs. It seems much more friendly to offer a restart option - or to even bake that in as
a deployment option. To put it a different way, if I say that VDB A imports the latest
VDB B, then I would have the expectation to in some way update A if a new version of B
comes online - otherwise I'm not really reusing B, but an old snapshot - they may not
even exist anymore.
Merge VDB action should provide way to persist the results
-----------------------------------------------------------
Key: TEIID-1366
URL:
https://issues.jboss.org/browse/TEIID-1366
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Affects Versions: 7.2
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 8.1
Currently "merge vdb" admin action is memory resident and does not persist
between server restarts. Need to explore way to make this action persistent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira