[
https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2875:
---------------------------------------
TEIID31152 More the one constraint with the name
my-model.my-schema.MY-FOREIGN_KEY_CONSTRAINT_NAME
I think that the check added for TEIID-2922 may be over zealous - or at least that the
importer should auto-resolve name conflicts because I think this is the second time
we've seen behavior like this where the same constraint, at least by name, is repeated
in the metadata. Could you log an issue, possibly with DDL that highlights the
situation?
Taking into account that this VDB is going to be used mostly for
reading (select querying), how do you think the performance of the VDB is affected by
setting the above property?
Knowing the keys assists with planning especially if you have federated joins. If you are
going mostly against a single source it's more of an issue of what metadata is
reported to your consuming app by Teiid.
Also, is there a way to exclude the individual constraints that are
causing the error ?
Unfortunately no. There is a more specific importForeignKeys importer setting though that
you could use.
Metadata failed to load. No column found
----------------------------------------
Key: TEIID-2875
URL:
https://issues.jboss.org/browse/TEIID-2875
Project: Teiid
Issue Type: Bug
Affects Versions: 8.6
Environment: Windows server 2003, Windows 7.
Reporter: SHI HONG CHIN
Assignee: Steven Hawkins
Attachments: JakkerData-vdb.xml
Affected database: Oracle
The following error displayed when Teiid loading a dynamic VDB:
10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB
JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column
found with name "RATE"."CHARGE_NAME"
10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB
JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column
found with name "RATE"."CHARGE_NAME"
I am not the one who design the database. But, I cannot find any table with above
mentioned column name in Oracle database. So, I am not sure whether the above mentioned
column name is a hidden column or not.
This bug does not exist in version 8.5.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)