[
https://issues.jboss.org/browse/TEIIDDES-944?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-944:
---------------------------------------
Thinking about it... makes sense that the hard-coded 7.4 API really can't be changed
in Teiid Designer unless we create some segmented part of our DQP code that goes along
with teiid_embedded_query.
Preview Data requires both an API call (Deploy) and a JDBC call to the SAME server. So
based on that, moving the 7.1 CP definition to use 7.4 is the right thing to do at this
time.
Users can STILL create create JDBC VDB CP's for 7.1 servers by finding a 7.1 client
driver jar. So there is some "backward" compatibility for Execute VDB IF the vdb
is already deployed on a 7.1 Server.
Add Teiid Server 7.4 Connection Profile Driver definition
---------------------------------------------------------
Key: TEIIDDES-944
URL:
https://issues.jboss.org/browse/TEIIDDES-944
Project: Teiid Designer
Issue Type: Sub-task
Components: Datatools Integration
Affects Versions: 7.4
Reporter: Barry LaFond
Assignee: Dan Florian
Priority: Blocker
Fix For: 7.4
7.4 release needs to be compatible with Teiid 7.4 client.
So we need to add a new driver definition to the org.teiid.datatools.connectivity
plugin.xml and any additional artifacts or definitions. Result should be that 7.4 Designer
Preview Data and Execute VDB actions create/use a 7.4 Driver definition BUT the option in
DTP to create a 7.1 Teiid driver is available.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira