[
https://issues.jboss.org/browse/TEIID-1328?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1328:
--------------------------------------
Here's want I want to do:
1) A delegate translator caches the results of the delegate's getMetadata call by
serializing the metadata store to disk
2) On VDB reload, the delegate translator provides the cached results using
setMetadataStore instead of delegating the getMetadata call
The question is, what is the key I should use to name the serialized metadata store so
that the delegating translator can provide the proper data in step 2?
Now, having gone through the code a little deeper, it looks like MetadataStore is a
singleton and not per translator as I originally assumed. Is this correct? If so, it
seems like we could cache the entire store in one operation and, on VDB reload, call
setMetadataStore with the deserialized singleton on each getMetadata call. A little
hacky, but effective.
Alternatively, I think we could be more individualistic by using the schema name as a key
to identify each individual connection/translator pair. If that's the case, it would
be convenient if you provided a public getSchema() method in the MetadataFactory.
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