[
https://issues.jboss.org/browse/TEIID-2253?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2253:
---------------------------------------
The common workaround for all of these issues is to use a partitioned union - see
https://docs.jboss.org/author/display/TEIID/Federated+Optimizations.
The intent of this issue is to update and rationalize the multi-source feature. Even if
the sub-tasks are addressed a core limitation of multi-source would be the requirement of
a homogenous schema (all tables/columns must share the same name) and for backwards
compatibility joins must implicitly specify tbl1.source_name = tb2.source_name - to
enforce that the partitioned join is used.
Multi-source isssues
--------------------
Key: TEIID-2253
URL:
https://issues.jboss.org/browse/TEIID-2253
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
The design of the multi-source feature has several issues that need addressed.
--
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