[
https://jira.jboss.org/jira/browse/TEIID-69?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-69.
---------------------------------
Resolution: Won't Fix
A full implementation of hashjoin should not be needed, rather we'll rely on dependent
joins and a partitioning optimization to merge join.
Fully implement Hash Join
-------------------------
Key: TEIID-69
URL:
https://jira.jboss.org/jira/browse/TEIID-69
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.x
Reporter: Steven Hawkins
Fix For: 7.x
Defect Tracker #24376: Based upon the old
com.metamatrix.query.processor.relational.HashJoinStrategy (now deleted, but can be
resurrectedfrom cvs) fully implement the hash join feature. Costing should be used in
RuleChooseJoinStrategy to look for situations in which merge joins are valid but that have
one side that is much smaller than the other (and preferable smaller than a processing
batch).
--
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