Bug 1270336 - Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates
Summary: Deploying a .vdb where a dynamic vdb has already been deployed, fails due to ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid, Tooling, Integration
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: 6.3.0
Assignee: jolee
QA Contact: Jan Stastny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-09 16:44 UTC by Van Halbert
Modified: 2019-01-07 14:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If you try to deploy a virtual database after a dynamic virtual database with exactly the same name has already been deployed, it will fail. To work around this problem, avoid mixing VDB types.
Clone Of:
Environment:
Last Closed: 2019-01-07 14:17:40 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-3747 0 Major Closed Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates 2019-01-04 15:10:07 UTC

Comment 2 JBoss JIRA Server 2015-10-12 14:11:44 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-3747 to Resolved
Comment 4 JBoss JIRA Server 2016-01-27 21:25:04 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-3747 to Closed
Comment 8 David Le Sage 2017-05-11 03:33:48 UTC 
I have amended the release note to indicate that they both have exactly the same name.
Note You need to log in before you can comment on or make changes to this bug.