We don't have cache delegates at the moment, but we would implement them for your needs, including a clustered swap. Tristan On 25/11/2015 18:00, Van Halbert wrote: > Maybe there's a version of cache delegates I missed. One of the options > was for Teiid to use/manage the aliases that mapped to the 2 caches. And > would be swapped when materialization process was performed. But an issue > with this is when there's a cluster of DV nodes, the name swapping would > have to be replicated across all the nodes. And DV doesn't have the means > to guarantee the name is changed on all nodes after the process is > performed. > > Van Halbert >

In the JDG translators, enable named cache swapping so that materialization can be supported -------------------------------------------------------------------------------------------- Key: TEIID-3725 URL: https://issues.jboss.org/browse/TEIID-3725 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.12 Reporter: Van Halbert Assignee: Van Halbert The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). Ideas are: 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use perform materialize load call SYSADMIN.setProperty to trigger the swapping of the cache names 2 ??? Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from.