[
https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-3725:
------------------------------------
Based on the latest conference call, it was decided that the teiid translator will be
changed to use a second JDG cache for managing the cache names. The key:value pairs will
be used to refer to: cache alias name: cache name
The cache alias names will be assigned accordingly:
modelName.tableName : jdgCacheNameA
modelName.tableName.stage : jdgCacheNameB
The translator will be changed to support native query, so that a specific native query
can be issued as part of the materialization process to handle pre-processing and
post-processing (swapping jdgCacheNameA/B).
There is more usability work to be done to assist with reverse engineering the view table
into a pojo object. Will start looking at that once the translator logic is done and in
the product build.
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)