[
https://issues.jboss.org/browse/TEIID-2326?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2326.
-----------------------------------
Resolution: Done
updated the logic to ensure that an imported vdb mat view is loaded as if it were in the
imported vdb. also added a combined classloader for vdb with imports.
It seems like a reasonable default to always share imported materialized views. There may
at some point still need to be a mechanism to tell teiid to not import an internal mat
view, but ideally it would be more granular than an entire vdb (perhaps a
VDBImport.excludeMatViews that is a list). Otherwise the workaround is to use an external
mat view and use alternative behavior based upon the vdb name/version.
Allow importing vdbs to share the materialized view of imported vdbs
--------------------------------------------------------------------
Key: TEIID-2326
URL:
https://issues.jboss.org/browse/TEIID-2326
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4
Currently the end importing vdb will be the owner of a distinct set of internal
materialized views regardless of whether those materialized views come from an imported
vdb.
--
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