[
https://issues.jboss.org/browse/TEIID-4730?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4730:
-------------------------------------
No, it is not using the wrong VDB name. The behavior as expected, but the error is
confusing and occurs at much later at a stage it would hard to figure out whats going on.
My thought is, is there anyway we can avoid or provide a better exception message.
options:
1) During the import of the VDB we can scan through the materialized views in the VDB, and
throw up a warning if any of them is not defined with correct scope for sharing.
2) Have a duplicated copy of materialization for enclosing VDB. This seems lot of work,
with many implications starting with having a second set of MAT_VIEW properties for view
in top level VDB. It just complicates the issue, which in real world usecases the intent
may be to share any way.
So, I can settle for option (1).
Problem with Import VDB with Materialized View (external)
---------------------------------------------------------
Key: TEIID-4730
URL:
https://issues.jboss.org/browse/TEIID-4730
Project: Teiid
Issue Type: Bug
Components: Common
Affects Versions: 9.1.2
Environment: * Teiid 9.1.2
* CentOs 7
* WildFly 10
Reporter: Pedro InĂ¡cio
Assignee: Steven Hawkins
Attachments: externalMaterializationOrderProblem-vdb.xml, numberingPlan-vdb.xml
Having defined a VDB which contains a Model that has External Materialization, when
importing this VDB into another that also uses External Materialization, Teiid Server is
searching in the wrong place for the view status.
Example:
..
<import-vdb name="CountryServiceListVDB" version="1"
import-data-policies="true"/>
...
<model name="MyView" type="VIRTUAL">
...
SELECT cns,
country_code
FROM NumberingPlan.numbering_plan;
....
</metadata>
</model>
*NumberingPlan.numbering_plan is defined in the imported VDB, and is also Materialized.*
*Warning in Logs: *
17:51:45,161 WARN [org.teiid.MATVIEWS] (Worker8_QueryProcessorQueue10653) n9M6de3y5xHM
org.teiid.jdbc.TeiidSQLException: TEIID30328 Unable to evaluate (SELECT
mvstatus('NumberingPlan', 'numbering_plan', Valid, LoadState,
'THROW_EXCEPTION') FROM (SELECT 1) AS x LEFT OUTER JOIN
NumberingPlanMaterialized.status ON VDBName =
'ExternalMaterializationOrderProblem' AND VDBVersion = '1' AND SchemaName
= 'NumberingPlan' AND Name = 'numbering_plan' LIMIT 2): TEIID30328 Unable
to evaluate mvstatus('NumberingPlan', 'numbering_plan', Valid, LoadState,
'THROW_EXCEPTION'): TEIID30384 Error while evaluating function mvstatus
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)