[ https://issues.jboss.org/browse/TEIID-4977?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4977: ------------------------------------- [~vhalbert2] See attached file for the example materialization that matches with the pre 9.3 methods with use of staging tables. You would need 3 different kinds of caches for this solution to work similar to previous JDG based example, but note the approach may be different entirely. You need 3 caches * MV (materializing for cached table, this name can be anything) * ST (staging per cached table, this name can be anything) * teiid-alias-naming-cache (cluster wide internal cache to keep track of aliased tables, must match the name, create as _replicated_ cache. This can be pre-configured with any Teiid deployment and keep user based configuration simple. When you enable "DirectQueryProcedure", the translator will start looking for "teiid-alias-naming-cache". If this cache is available then the aliased table feature will kick in. Also, when "DirectQueryProcedure" is enabled, there are two commands supported through this mechnisam * truncate <full-qualified-table-name> ==> clears the whole cache * swap <from-table> <to-table> ==> swaps the tables from from 2 to, to 2 from An example VDB attached, can take look and test it, and give me feedback. Also, I will let you document this for 6.4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)