[teiid-issues] [JBoss JIRA] (TEIID-4765) The notion of resolving order may need to be extended beyond a schema
[
https://issues.jboss.org/browse/TEIID-4765?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-4765.
-----------------------------------
Fix Version/s: 9.2.1
Resolution: Done
Took a couple of steps in this direction. The most direct was not allowing the processing
of general schema level ddl until after schema are declared and imports are processed.
However we are still not fully in alignment with how metadata is processed from a vdb.xml.
That can be made even more consistent with TEIID-4536
Another part of this is ddl generation is based upon resolving order, and not just
type/name. Eventually if we round-trip through a live metadata system the order of the
statements will matter - for example a referenced table or view must exist for use in
later statements.
The notion of resolving order may need to be extended beyond a
schema
---------------------------------------------------------------------
Key: TEIID-4765
URL: https://issues.jboss.org/browse/TEIID-4765
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.3, 9.2.1
With TEIID-4629 it is possible to interleave the definition of schema elements, which is
not accounted for by the loading order - and will fail upon later validation/resolving.
create virtual schema first;
create virtual schema second;
set schema second;
create view x ...;
set schema first;
create view y as select * from x;
the last statement will fail later as we'll try to resolve the schemas in order.
A similar issue exists with create domain - TEIID-3624
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)