[
https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-1366:
-------------------------------------
+1 for option (1). This will reduce the amount of changes that need to be done in
tooling.
I did not understand the reason for the admin operation, the VDB metadata for respective
vdbs is loaded at the time of deployment, why do they need to update their metadata after
merge? As a general feature to update their metadata this operation is useful, I see that
in merge case metadata needs to be handled differently.
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