[teiid-issues] [JBoss JIRA] (TEIID-2578) add/remove schema elements

Ramesh Reddy (JIRA) issues at jboss.org
Tue Oct 18 22:39:00 EDT 2016


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

Ramesh Reddy commented on TEIID-2578:
-------------------------------------

>> 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.

User has the ability to carry out this operation, it is not just tied to the restart/redeploy option. It provides a different way to update, so IMO this is OK as long as there is way to do this.

On VDB import I agree. How about something like

CREATE SCHEMA {name} IDENTIFIED BY DATABASE x VERSION  y  SCHEMA z; 

and mark the imported metadata as READONLY and not allow any ALTER  or persistent operations.

>>Not yet, they require a RuntimeVDB acquired from the VDBService, which is not associated with a DDL based VDB.
I know I worked on this, I do not think I ran through all the methods.

I do not think we can have this as complete replacement with other behavior wise, especially when there is no external concept of deployment. But if want to go towards the deployment based, we can simply provide *-vdb.ddl based deployer back into this without much hassle, but we would not support ALTERS on that. 

> 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)


More information about the teiid-issues mailing list