[
https://issues.jboss.org/browse/TEIID-2416?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2416:
----------------------------------
Component/s: Connector API
Query Engine
When should this be targeted? Do we want to first focus on getting a better api for
Embedded (mostly around configuring the metadata) or simultaneously produce a tech preview
for JDBC development?
Should TEIID-167 be made a subtask of this? And generally do we envision both a rar and
non-rar mode? The former could possibly be an enhanced embedded kit with ironjacamar.
Create a JDBC driver SDK
------------------------
Key: TEIID-2416
URL:
https://issues.jboss.org/browse/TEIID-2416
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
We should promote an offering of Teiid as just a JDBC toolkit via translator development
with an emphasis on a minimal footprint (starting with Embedded, but possibly allowing for
the exclusion of large dependencies - primarily saxon, but also xom, nux, etc.).
More than likely a simplistic configuration scenario via the TeiidDataSource/TeiidDriver
would be offered.
There would be a well-documented and straight-forward migration path to full server
deployment as well.
We should also put more thought into the pass-through sql scenario for additional
flexibility in issuing queries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira