[
https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-143:
------------------------------------
The concern with file based loading is, server keeps a copy of the jars in the DB. In
cluster situation they can get out of sync.
If connectors does not need DB based extension class loading, we can make this this work.
i.e. Connector are loaded during the startup, every cluster member defines their own
connectors and their dependencies in their installation directories. This may be a good
thing. However to patch a connector you would require manually copy the jar to each
cluster member. Patching though Console or Admin api would be cumbersome, as they not be
dealing same version of the Connector.
Another requirement I should add is
6) Package them easy enough to expose them as plugins in the eclipse, so that they can be
used as sources for metadata importing and as well as use under Embedded execution in
Designer as connectors.
Query should 'find' connector types and jars rather than have
them predefined in the config.
--------------------------------------------------------------------------------------------
Key: TEIID-143
URL:
https://jira.jboss.org/jira/browse/TEIID-143
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 6.0.0
Reporter: John Doyle
Fix For: 6.1.0
Original Estimate: 1 week
Remaining Estimate: 1 week
Currently, dqp as delived with Designer is preconfigured with connector types. I think
it should discover the connectors that are available upon startup. This would make it
easier to add connectors to a kit. The current process for adding a connector to a kit is
manual and error prone. We have problems with it on nearly every release.
This is also an attractive feature for embedding query in other environments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira