[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 1/12/16 1:00 PM:
-------------------------------------------------------------
The native queries are currently looking like:
Before native query format:
{code}
truncate cache
{code}
After native query format:
{code}
swap cache names
{code}
changed to remove the cache names on the native query as the resource adapter will have
this configured.
was (Author: van.halbert):
The native queries are currently looking like:
Before native query format:
{code}
truncate cache {stageCacheName} {aliasCacheName}
{code}
After native query format:
{code}
swap cache names {primaryCacheName} {stageCacheName} {aliasCacheName}
{code}
where:
primaryCacheName - is the cache that could already be available
stageCacheName - is the second cache to be used in materialization
aliasCacheName - is the cache to persist the cache alias names key<String>
--> value<String>
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)