[
https://issues.jboss.org/browse/TEIID-3530?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3530:
---------------------------------------
Made the initial commit. This added an optional JDBC parameter to control whether
dependent join values are bind values or not. It will default to false for oracle, but
otherwise will be true. Although in testing it did not appear that newer versions of
oracle, such as 12, had a problem with large prepared statements.
Removed the dependentJoinPushdownThreshold and instead looked at the additional processing
that could be performed. If there is significant post-processing then even without a
hint, we'll fully push the dependent join. We will need to expand the hint syntax to
also prevent this from happening.
Also the dependent criteria processor will not use the key only temp table method for
simple/small dependent joins. The tuning for that seemed fairly consistent for oracle and
sql server sources.
dependent join enhancements
---------------------------
Key: TEIID-3530
URL:
https://issues.jboss.org/browse/TEIID-3530
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
We need to address several aspects of dependent joins:
- allow for translators to control if bind variables will be used (oracle should not)
- remove the dependentJoinPushdownThreshold option and allow the planner to fully push
the join based upon the plan
- have rule choose dependent make a better determination of when to use a temp table vs.
in predicates.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)