[
https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2578:
-------------------------------------
>It seems like if a non-master cluster member comes up after any
changes have been made, it won't have those changes synched until after the vdb is
reloaded by another change.
In this singleton service scheme, only master should
have the persistent copy of VDBs, so if non-master node comes up it should be empty to
start with. As soon as master node starts it should replicate the events. (atleast that is
what I think :) ), but issue could be, what if master node went down in-between and comes
back up, it is going to duplicate the state, that needs to be avoided. I did not add any
provision for this, IMO we need to maintain a VDB wide version/lastmodified number that
can be passed with *all* EventDistributor methods. aka. like a if-match-none HEADER in
http, What do you think?
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)