[
https://issues.jboss.org/browse/TEIID-2253?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2253:
---------------------------------------
I've been spending some time with trying to make the multi-source logic more
consistent as part of this overhaul. It looks like we'll end up with a very different
implementation than we do now. Of current logic is based upon the idea that the plans
will be mostly pushdown/simple such that the effect of the multi-source operation can be
localized to the access nodes. In general this is not the case, for example if
multi-source tables end up on both sides of a join, in a with clause, on both sides of an
insert into, etc. the current logic does not correctly interpret the intent. The approach
of disabling all ordering/aggregate capabilities is also not ideal as it should only
affect the user query.
Multi-source issues
-------------------
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