[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- I was only thinking to expose this layer to engine to begin with, so client based requests are not involved to modify the vdb metadata. But that could be an addition. With this available to the engine, then use for materialization as source table creation. I understand what you are saying about the ddl generation and creation of indexes, but for that I do not want to take extension metadata from designer, I was thinking I would rather use hibernate facilities for JDBC (like how you did for the temptable), and leave up to the translator implementation for supporting other source types. So, effectively I would like to treat matviews as always external, if the source is missing route to a known internal translator, which is effectively the current global temp table store or could be a java db. There is whole lot of code in temptable/materialization, trying to understand it first. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira