[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- To an extent. You loose ease of use of metadata reload in the import schema case. That is something we could workaround by adding a high-level operation that drops all the objects of the schema, then reruns the import as part of a "restart" operation. However we are fundamentally breaking the expectations of the vdb reuse feature. The reuse here is now only at the time of the import statement - any further changes to the imported vdb require a manual process on the part of the user to incorporate into all importing vdbs. I don't see a simple workaround here since the load operation from the databasestore assumes everything is fully realized and in a valid state. The load will need some work in general as any issue with any vdb load will cause the whole load to be aborted. Not yet, they require a RuntimeVDB acquired from the VDBService, which is not associated with a DDL based VDB. I'm a little uncomfortable with that if it means they have different capabilities/behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)