[
https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2249:
---------------------------------------
Pushdown of the entire join may be done as a variation of common table pushdown, where a
tuplesource is provided to define a common table (other details such as index creation,
etc. TBD). That would likely follow in 8.5 or later.
For 8.4.1 I am thinking that we'll add an additional configurable translator property
along the lines of "dependentJoinPushdownMinimum". This would likely be an
integer indicating that dependent joins exceeding that number of distinct independent
values should be pushed down. Presumably a user would set it to a value that would be
over what would be performant with several in pushdown queries (even when executed in
parallel) such as 100000 independent values.
Then the option makedep and positional makedep hints would be altered to all for the
additional specification of dependent join options - option makedep tbl (min:50000 join)
Here min would override the translator property and join would indicate that the whole
join would be pushed down.
Enable the use of temporary tables for those data sources that
support them instead of IN criteria for EDS
----------------------------------------------------------------------------------------------------------
Key: TEIID-2249
URL:
https://issues.jboss.org/browse/TEIID-2249
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Fix For: 8.4.1
Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather
than creating a long 'IN' list, inserting them in to a temporary table - for
example a # table in Sybase and SQL Server - and then generating an SQL join to that
instead.
One of the difference to materialized views (or at least my understanding), is that this
work happens at a data-source rather than within the Teiid server.
--
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