[
https://jira.jboss.org/jira/browse/TEIID-684?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-684:
--------------------------------------
The initial check in had any additional setting for import on the connector binding,
however to be more aligned with the way the designer does imports (which allows for more
advanced scenarios) it would be good to allow them to be specified on the model info in
the ConfigurationInfo.def. That way the same connector binding could be used for multiple
"models" built from different import settings.
Dynamic data integration feature (Integrate data with out a VDB)
----------------------------------------------------------------
Key: TEIID-684
URL:
https://jira.jboss.org/jira/browse/TEIID-684
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Critical
Fix For: 6.2.0
This is feature request for dynamically integrating the data with out any modelling
exercise, so that any tooling is not required before you can start integrating data.
Using this feature, the user would create/define a Connectors (data sources) in the Teiid
runtime engine, and then user connects to runtime engine using the JDBC driver provided,
then he/she can start writing SQL queries that spans multiple data sources in a single
statement as if they are single source.
For example:
Data Source: A has
TableA1
TableA2
DataSource: B has
TableB1
TableB2
user can write SQL queries such as
SELECT A.TableA1.e1, A.TableA1.e2, B.TableB1.e1, B.TableB1.e2 FROM A.TableA1, B.TableB1
WHERE A.TableA1.e1 = B.TableB1.e1
They can much more complex join queries than above too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira