[
https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5394:
-------------------------------------
If you are suggesting to do that at runtime, that's not much
different than what I'm suggesting.
I am saying if you need to separate ddl files per schema to support import schema,
let's put that as a restriction, no reason to be flexible.
You may want to alter the current behavior. See the .vdb from
rdbms-as-datasource, it will contain the yaml as described above.
You are correct, it is picking up resources folder. I have to test if that is needed or
could be omitted. Even if we did, that should be served as a configuration template as the
values for most properties should flow in from environment variables.
Also a .ddl file is not covered by the maven plugin logic. Was that
intentional?
Are you asking for top-level VDB? if yes, that is true, I did not put in support for .ddl
initially was not sure if that worked in zipped archive
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.1
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)