[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=13147826#comment-13147826 ] 

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

Comment from Adrian regarding improving usability of materialization:

So by "DV will reverse engineer from a table into the pojo to be used" 
you mean DV will generate the pojo source code based on the columns DV 
discovers in the db table? In that case it could also annotate its 
java-bean like properties with our protobuf annotations (see Infinispan 
Query Guide JDG 6.5, section 7.3.7). The protobuf schema would be 
internally generated by JDG by inspecting those annotations, it will 
also generate the entity marshallers so it would save DV a lot of work. 
The process is described in [1].

Adrian

[1] 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.5/html/Infinispan_Query_Guide/sect-Protobuf_Encoding.html#Defining_Protocol_Buffers_Schemas_With_Java_Annotations

Status:

The ability to perform materialization when JDG is in library mode has been done and tested.   The jdg-local-cache quick start needs cleanup, but is essentially done.  

The next step is to make the changes to the connector-infinispan-dsl resource adapter so that it handles the cache aliasing as the connector-infinispan.6 resource adapter (library mode).   Also, based on Adrian's suggestion, I'll go ahead and add the logic to check the class for protobuf annotations so that the cache can be configured accordingly.  

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