[teiid-issues] [JBoss JIRA] (TEIID-1366) Merge VDB action should provide way to persist the results

Tue May 1 16:39:25 EDT 2012

    [ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689260#comment-12689260 ] 

Steven Hawkins commented on TEIID-1366:
---------------------------------------

There are two possible modes of operation here.

1. an imported vdb is operationally separate from the parent
  - this is mostly how the merge vdb logic currently works.  however the same metadata objects can be used between two different vdbs, thus operations that modify the metadata can have an effect on both vdbs.

2. an imported vdb is treated as a fully dependent entity
  - in this case events such as the removal of the dependent vdb should render the parent vdb inoperative.  on the other hand we could look at sharing cache entries (in particular mat views).  This is quite a bit more work.

We should also look at adding an admin operation to restart a vdb, which is useful in case 1 and for dynamic vdbs as a way to update their metadata without a redeploy.

> 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