[
https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2584:
-------------------------------------
Will make suggested changes. Also will add exception handling for insert call.
And in theory the management of the materialized tables can be quite
complicated. We have logic in the internal materialization stuff about sharing imported
matviews, something like that may be needed here as well (although that complicates the
notion of what vdb/version a materialization table is from). Also people may want
materialization tables to be shared among vdb versions and selectively destroyed with a
new deployment.
For this, how about adding metadata flag on the view if this that can specify the sharing
scope, valid values can be {NONE, VDB, SCHEMA}, where
NONE = no sharing (default)
VDB = sharing across all the vdb versions
SCHEMA = sharing across multiple VDBs, if SCHEMA names match
I would have to change selection criteria based on this flag on the status table, seems
like that should work.
What would a partial load script do?
it another script provided
by user to incrementally load the matview updates, like the load script which does the
full updates.
I will read the PDF now.
Add management features to materialization
------------------------------------------
Key: TEIID-2584
URL:
https://issues.jboss.org/browse/TEIID-2584
Project: Teiid
Issue Type: Feature Request
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Labels: Beta3
Fix For: 8.5
Currently Teiid supports internal and external materialization features. The internal is
managed completely by the Teiid query engine along with the infinispan cache.
External materialization is completely unmanaged and left out to the user to manage it
externally. This goals for this feature are unify the materialization logic for internal
and external, such that both are managed similarly irrespective of the type of
materialization chosen.
--
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