[
https://issues.jboss.org/browse/TEIIDDES-3064?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-3064:
------------------------------------------
This will likely be supported for Teiid 10. As part of TEIID-2578 Ramesh was already
looking to support this, but that is not fully ready yet. There are a lot of issues to
work through though, the primary one being ownership/scoping as the datasources are server
wide.
Create EAP translator
---------------------
Key: TEIIDDES-3064
URL:
https://issues.jboss.org/browse/TEIIDDES-3064
Project: Teiid Designer
Issue Type: Enhancement
Reporter: Tom Johnston
Creating an EAP translator would allow for DDL to be used to create EAP items such as
datasources).
Where a source model table (foreign table) is bound to a JNDI, why not allow the creation
of the JNDI as a part of the overall model.
I.E. Create Foreign Source <ForeignSourceName> using <Translator> with JDBC
URL 'xxx'
this way when creating Foreign Tables you would refer to the ForeignSource similar to
DBMS's (i.e. create table xyx as select xxx from table@datalink)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)