7:32 p.m.
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: chorus-vdb.xml
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
7:32 p.m.
[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Andriy Rokhmanov updated TEIID-1867:
------------------------------------
Attachment: chorus-vdb.xml
Sample VDB with two multi-source models defined.
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: chorus-vdb.xml
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
7:34 p.m.
[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Andriy Rokhmanov updated TEIID-1867:
------------------------------------
Attachment: select.txt
Results of select * from sys.tables;
Shows the duplicate tables.
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: chorus-vdb.xml, 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
7:36 p.m.
[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Andriy Rokhmanov updated TEIID-1867:
------------------------------------
Attachment: both_multisource.jpg
Screenshot. Two multi-source (file-based and h2) models defined. See the duplicate stored
procedures in both schemas.
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
7:36 p.m.
[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Andriy Rokhmanov updated TEIID-1867:
------------------------------------
Attachment: one_multisource.jpg
Single multi-source model defined. No issues.
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
10:46 p.m.
[
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
6:58 a.m.
[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1867:
------------------------------------
Would it make sense in designer to add a warning that there are duplicate source names in
a vdb?
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
7:53 a.m.
[
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
9:48 a.m.
[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1867.
-----------------------------------
Fix Version/s: 7.6.1
8.0
Resolution: Done
Added two validations when creating connector managers. First we will ensure that all
source names are unique for each model. Second we will ensure that if the same source
name is reused that it refers to the same source (translator/connection).
Van, in Designer someone would currently have to manually modify the vdb to produce
duplicate source names (they default to the model name, which must be unique) or enable
multi-source. They will need more validation whenever they provide multi-source gui
support.
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
Fix For: 7.6.1, 8.0
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
5:19 a.m.
[
https://issues.jboss.org/browse/TEIID-1867?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1867.
---------------------------------
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
Fix For: 7.7, 8.0
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
4602
days inactive
4758
days old
9 comments
6 participants
participants (6)
-
Andriy Rokhmanov (Created) (JIRA) -
Andriy Rokhmanov (Updated) (JIRA)
-
Steven Hawkins (Commented) (JIRA)
-
Steven Hawkins (JIRA)
-
Steven Hawkins (Resolved) (JIRA)
-
Van Halbert (Commented) (JIRA)