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

[Van Halbert (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148924#comment-13148924 ] 

Van Halbert commented on TEIID-3725:
------------------------------------

I don't disagree that its not optimal.   However, until the latest releases of JDG, are there options to do all the configuration from the client side (i.e., configure protobuf on the server from the client).     Which would now enable the resource adapter to be more flexible.     But that would be a major change in configuration/migration for what's already available.     So I've resisted making sweeping changes that would cause compatibility issues.   Unless we want to create a brand new  resource-adapater/translator for users to transition to.

> 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)