[
https://issues.jboss.org/browse/TEIID-1328?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1328:
--------------------------------------
Sorry, just saw this.
To clarify our use case: we have data sources that come and go. To support this, we
We know when these events occur and could programatically trigger a redeploy using the
admin API. The only real problem with this approach is that it causes every metadata to
be reloaded from every model. For some of our models, this is prohibitively expensive.
As I see it, there are a couple of possible solutions: (1) as Steve points out above, we
could add/remove source models to VDB (we only care about dynamic VDBs) (2) a special
redeploy mechanism indicating that certain source models can re-use previous metadata
API request: Programatically modify the VDB
--------------------------------------------
Key: TEIID-1328
URL:
https://issues.jboss.org/browse/TEIID-1328
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Affects Versions: 7.1
Reporter: Mark Addleman
Priority: Minor
I'd like an API to programatically modify the VDB. It would be ideal to modify the
VDB using DDL through Teiid. Our primary use case is accessing a dynamic set of
datasources through Teiid. When a datasource is added, we would INSERT the appropriate
entries into MODEL, PROPERTIES, DATASOURCES tables. Teiid would reread the appropriate
metadata from the associated translators.
--
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