[
https://issues.jboss.org/browse/TEIID-5668?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5668.
-----------------------------------
Fix Version/s: 12.1
12.0.1
11.2.3
Resolution: Done
There have been several issues related to this style of query. In limited circumstances
we are allowed to push the aggregation to one side of the join - but having aggregates on
each side that are cardinality dependent is not something that the logic fully accounts
for. For now the fix is to not push the decomposed aggregation.
Wrong results on left join + aggregation
----------------------------------------
Key: TEIID-5668
URL:
https://issues.jboss.org/browse/TEIID-5668
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 12.0
Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core
6.0.2.Final)
Reporter: dalex dalex
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.1, 12.0.1, 11.2.3
Attachments: wrong_count_results_1.jpg, wrong_count_results_2.jpg
When using a query with a left join between tables from different schemes and count it
produces wrong results. The workflow for reproducing the bug contains two example queries.
The only difference between these queries is the order of the counts in select clause. The
first query returns wrong results (the output of the "count(b.SalesPersonID)"
field).
Additional info: a) the wrong count results are the distinct values b) occurs also with
other aggregations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)