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

[Ramesh Reddy (JIRA)]

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

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

On second that I do not think we wnat -vdb.ddl based deployment at all, there not much value at all in that. 

>> inverted the role of DatabaseStorage, so that DatabaseStore is primary. Also combined PersistenceProxy and DatabaseStorage.
BTW, I reason behind this was DatabaseStorage is extension point for user to provide additional storages, where as the DatabaseStore is engine controlled, no user extensions here. PersistenceProxy is fine, as I mentioned before, this needs to be expanded for finer grade methods, since I was just doing file based persistence I took block methods for time being.

>> we need to address the potential consistency issues with alter to prevent the entire vdb / repository from becoming unusable.
The way I was trying do this is unless the metadata is valid, it will not make it into DatabaseStore, thus keeping it pristine. You are correct, in order to do it correctly, we need like SNAPSHOT of changes that can be overlaid on DatabaseStore, and validate. I could not think of a cleaver way to do this with out duplicated whole state of DatabaseStore. Needs a rethought here.

>>databasestorage service has some wait cycles. shouldn't it just be able to wait for services?
yeah, the data sources availability could not tie it, on server restart while loading the VDBs from repo, these will get ahead of the system start. This needs to wait until system started then it can do the loading. Then this can avoid creation of data sources if they exist. I think this can be avoided, need to take another look.

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