-
Feature Request
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
Documentation (Ref Guide, User Guide, etc.), Release Notes
-
Medium
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.
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-167be 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.