[
https://issues.jboss.org/browse/TEIID-4977?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-4977:
------------------------------------
Here's what I was thinking:
- configure 2 tables on the model, where each table configures its cache name
- on the RA, configure the name of the cache used for managing the alias cache names,
where table cache name ==> cache name in use
- could copy the same procedure logic for swapping and truncating the cache, and swapping
the assigned names in the alias cache
- the RA, when a alias cache is defined, would get the cache name to use from reading
alias cache, otherwise, use whats passed in
questions:
- how to initialize the alias cache with the defaults
could use: OPTIONS(UPDATABLE 'TRUE', "OBJECT_NS:primary_table"
'MCE_AwardBookingClassJDGSource.MCE_AwardBookingClass');
and this could be used to initial the alias cache defaults, so that you know which to 2
tables are linked
just thinking.
Support materialization as the 8.12.x version did
-------------------------------------------------
Key: TEIID-4977
URL:
https://issues.jboss.org/browse/TEIID-4977
Project: Teiid
Issue Type: Feature Request
Components: Infinispan
Affects Versions: 8.12.x-6.4
Reporter: Van Halbert
Assignee: Ramesh Reddy
Priority: Critical
Need to enable the materialization process to load the cache "offline" and not
impact access to current cache and data. This would be similar to how the 8.12.x version
was implemented and similar to how RDBMS materialization is done.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)