[teiid-issues] [JBoss JIRA] (TEIID-2062) Produce an embeddable Teiid engine
[
https://issues.jboss.org/browse/TEIID-2062?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2062:
-------------------------------------
- I think we need to scope this to a single VDB. I can not think of a reason to allow
multiple vdbs. But may be allow multiple instances of it in given VM.
- Why only dynamic VDBs?
- By default it should only use the calling thread, that will remove the thread pool
usage. or let the user supply the thread pool as configuration.
- The usage pattern must allow outside a JEE container, so may be better off not relaying
on Workmanager stuff. But not sure how we can handle the transactional semantics.
- I like the "ConnectionFactoryProvider" enhancement, as it can not really
depend on JNDI tree to be available.
- Why replication? are you thinking we need to allow multiple embedded instances to share
state in clustered environment?
Produce an embeddable Teiid engine
----------------------------------
Key: TEIID-2062
URL: https://issues.jboss.org/browse/TEIID-2062
Project: Teiid
Issue Type: Enhancement
Components: Embedded
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Teiid's federation and query processing features are of use to several other
projects. An embeddedable form is desired such that:
- the application server is not required
- queries could be issued in the engine object model to by-pass parsing/validation and
results retrieved without the need for JDBC
- new translators could be added
The following would be open for discussion:
- the inclusion of saxon/xom/nux for SQL/XML processing
- if the general deployment logic would be needed, or if just a single dynamic vdb is all
that is needed
See the org.teiid.jdbc.FakeServer in the test-integration/common module for a rough
approximation at the entry point for a embeddable server. Note that it is more geared at
unit testing JDBC/ODBC rather than providing the features needed here.
--
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