[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1867:
---------------------------------------
Van, it may already you would have to check. That doesn't come into play here since
it's the dynamic case. The resolution will more than likely be that source names just
need to be unique to a model. Although that is really only to support the case of
splitting models for the same source(s). Since all of the sources are distinct in this
issue, it's proper to use unique source names.
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