[teiid-issues] [JBoss JIRA] (TEIID-2062) Produce an embeddable Teiid engine

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700193#comment-12700193 ] 

Steven Hawkins commented on TEIID-2062:
---------------------------------------

To answer each:
- There's no need to limit to 1.  Unless we simplify surrounding APIs to not have name/version, there's no real benefit to doing that.
- That's just a simplification of the deployment method and there's no expectation that designer will be used.  Designer vdbs could be added if needed we would just have to add more complete handling for the notion of a vdb.xml (currently there is no need) and call to the index loading logic.
- Yes, we are using the calling thread by default, but we are still allowing for parallelization in non-transactional and XMLTable scenarios.  And yes if userRequestSourceConcurrency is set to one, when we could set the engine thread pool to just a direct executor.
- Yes, it's generally helpful to have that for our unit testing as well.
- Yes, there's no reason why an app cluster couldn't share their cache entries, replicate events, etc.  However like I say unless we pull out jgroups/infinispan related service code from jboss integration I don't expect that this would actually be used.  The EmbeddedServer currently allows for setting an ObjectReplicator at the very least so that the replication integration test can still run.
                
> 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