]
Van Halbert commented on TEIID-3725:
------------------------------------
Just completed the changes and testing with supporting materializing to a remote cache.
These changes will include the following:
- added materialize configuration examples to the docs/teiid/datasources/infinispan
- updated the jdg-remote-cache example.
- eliminated the use of the JDG remote-query quick start, by coping that code into the
teiid jdg-remote-cache quick start because there are changes to the configuration of the
materialize caches that were needed.
- this also includes the refactoring of the infinispan-dsl resource adapter
(TEIID-3559).
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.