[teiid-issues] [JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3725 at 12/16/15 11:58 AM: --------------------------------------------------------------- There will need to be 3 caches in order to do materialization: - the primary cache used for reading - the staging cache to load using materialization - a cache used for tracking the cache name aliasing that will be used. This will enable the underlying translator logic to swap out the cache (i.e, primary versus staging) after the cache that was used for staging is loaded and provide a persistence of the aliasing when the server is restarted. Another reason for needing the 3rd cache is that the other caches will be completely cleared before each materialization. So combining different object types into a cache wouldn't work at this time. The configuring of the caches to be used will be done on the connector, along with configuring the other JDG connection information. I contemplated using translator overrides for this additional settings, but decided on the connector because the connector settings are specific and the staging cache settings would be specifically related to that same cache. was (Author: van.halbert): There will need to be 3 caches in order to do materialization: - the primary cache used for reading - the staging cache to load using materialization - a cache used for tracking the cache name aliasing that will be used. This will enable the underlying translator logic to swap out the cache (i.e, primary versus staging) after the cache that was used for staging is loaded and provide a persistence of the aliasing when the server is restarted. The configuring of the caches to be used will be done on the connector, along with configuring the other JDG connection information. I contemplated using translator overrides for this additional settings, but decided on the connector because the connector settings are specific and the staging cache settings would be specifically related to that same cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)