[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1867:
---------------------------------------
The logic currently expects all source names to be unique. So what is happening is that
we're using the same ds1 for both metadata loads. The workaround is to just use
distinct source names.
It is valid to use the same datasource for multiple models, so it would make sense if the
source name were allowed to be unique to just the model.
Duplicate metadata for multisource models
-----------------------------------------
Key: TEIID-1867
URL:
https://issues.jboss.org/browse/TEIID-1867
Project: Teiid
Issue Type: Bug
Affects Versions: 7.5
Environment: Windows 7, JBoss 5.1.0, java version 1.6.0_22 - 64 bit.
Reporter: Andriy Rokhmanov
Assignee: Steven Hawkins
Attachments: both_multisource.jpg, chorus-vdb.xml, one_multisource.jpg,
select.txt
When more than one multi-source model defined in single VDB, the tables from one
multi-source schema appear in the another one. See screenshot and sample vdb attached. The
issue reproducible on our side with file, h2 and hsqldb multi-source models. We have to
define only one multi-source model per vdb to avoid the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira