[teiid-issues] [JBoss JIRA] (TEIID-5394) Define how to utilize multiple vdbs

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-5394:
-------------------------------------

> only for xml based vdbs (ddl with the current restrictions is potentially supportable)
What other kinds of VDBs are you thinking about? this should handle XML VDBs with external DDL files. I am expecting the original VDB in their project's "vdb" directory for this plugin, the contents will be in exploded format. i.e. if I were to take Designer's new VDB format with ddl files, I would place them in exploded format in my maven project. I do not think we have anyone just using the just DDL based vdb.

> you have to create an appropriate uber config yaml for the importing vdb
I am keeping all the configuration out of VDB layer. The previous version of the plugin by default copied the project-default.yaml file, but I commented out that for VDB building. Yes, you are correct, since we no longer have single server deployment model configuration needs to be (re)defined, I see that as an issue with this immutable deployment model than this VDB import process itself.

> requires the use of semantic versioning
I do not think I follow this one, you mean because we are using the maven versioning scheme?

> It also may need to handle the merge of vdb properties.
I did not realize we are doing this in the server code, will have to take peek. Should be a simple change. Same with data roles related changes looks like we need to do more introspection there than blind copy.

> Having a child vdb with imports wouldn't be an issue correct? 
I have explicitly not allowed the nesting of imported VDBs. IMO, it is a matter of building multiple projects on the developer side, I believe that is exactly what are you saying too.

> Define how to utilize multiple vdbs
> -----------------------------------
>
>                 Key: TEIID-5394
>                 URL: https://issues.jboss.org/browse/TEIID-5394
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Build/Kits
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 11.2
>
>
> Perhaps to support vdb imports, we should define how a build can incorporate multiple vdbs.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)