[
https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2578:
-------------------------------------
>import operations have different semantics than the declarations
in a vdb.xml where schema imports can be redone on restart/demand and vdb imports are
based upon the service.
Yes, these semantics are different. The way I am viewing
this is, the act of restart/redpolying of the VDB or someone explicitly updating the
schema, both are actions taken by the user. With this we are some what similar to other
databases.
>there is no service / runtime vdb created for the ddl based vdbs.
all of the admin VDBOperations won't work correct?
They should work, the service
is required so that we can tie a deployment artifact to the VDB. Since here there is no
deployment of the VDB then that layer is not needed. I had to move some functionalities of
other services around but it should work.
I see the benefits of deployment and repository based vdbs, we need to articulate both
positions in examples and documents to choose what is better for the user.
add/remove schema elements
--------------------------
Key: TEIID-2578
URL:
https://issues.jboss.org/browse/TEIID-2578
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 9.2
Schemas are currently static after load. Modifications can only happen with restarts or
new versions. We should allow add/drop at runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)