[
https://issues.jboss.org/browse/TEIID-2146?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2146.
-----------------------------------
Resolution: Done
changed the sortutility to only add the remaining columns for dup_remove_sort, not
dup_remove. also updated the DependentCriteriaProcessor distinct value checks - but that
change is not required for backporting.
Dependent join independent dup removal issue
--------------------------------------------
Key: TEIID-2146
URL:
https://issues.jboss.org/browse/TEIID-2146
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 8.1
If a dependent join uses columns from the independent side beyond the join predicates and
has unique values with duplicates for the predicate value from the independent side, then
the duplicate removal will fail to remove the duplicates, since it is mistakenly using all
columns.
If the duplicates then span multiple dependent queries, such as would be the case with
large dependent joins or when a source is used with limited value pushdown (such as
sybase), then the join result can be incorrect with duplicate rows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira