[teiid-issues] [JBoss JIRA] (TEIID-4934) Allow importing VDBs with conflicting model

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412449#comment-13412449 ] 

Ramesh Reddy commented on TEIID-4934:
-------------------------------------

I guess if we treat if the same named VDB is being loaded again, or recursively if omit it, or if same named model is being loaded then avoid loading based on flag might work. Teiid may need to load import vdbs as the last action.

> Allow importing VDBs with conflicting model
> -------------------------------------------
>
>                 Key: TEIID-4934
>                 URL: https://issues.jboss.org/browse/TEIID-4934
>             Project: Teiid
>          Issue Type: Enhancement
>    Affects Versions: 9.2.3
>         Environment: * Wildfly 10
>  * Teiid Server 9.2.3
>            Reporter: Pedro Inácio
>            Assignee: Steven Hawkins
>
> It should be possible to import a model via "_import-vdb_" that conflicts with other models also imported via "_import-vdb_" if the conflicting model has the same version.
> This will allow greater model reuse, and not to have duplicated model definitions in multiple vdbs.
> Example:
> VDB 1:
> <code>
> <vdb name="OneVDB" version="1">
> 	<description>One VDB</description>
> 	<import-vdb name=ConflictingVDB" version="1"/>
> 	<import-vdb name="OtherVDB" version="1"/>
> </code>
> VDB 2:
> <code>
> <vdb name="TwoVDB" version="1">
> 	<description>TwoVDB</description>
> 	<import-vdb name=ConflictingVDB" version="1"/>
> 	<import-vdb name="YetOtherVDB" version="1"/>
> </code>
> VDB 3:
> <code>
> <vdb name="ThirdVDB" version="1">
> 	<description>Third VDB</description>
> 	<import-vdb name=OneVDB" version="1"/>
> 	<import-vdb name="TwoVDB" version="1"/>
> </code>
> Currently we cannot use the ThirdVDB as is, since there is a conflicting VDB (ConflictingVDB) defined in VDBS One and Two.
> Since both are using the same version, it should be possible to ignore the conflict (via a property for example).



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)