[
https://issues.jboss.org/browse/TEIID-4727?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-4727.
-----------------------------------
Fix Version/s: 9.0.6
9.2
9.1.3
Resolution: Done
My initial assessment was incorrect. It was more of an issue when the aggregation was
targeted at a non-access node. That needed to be handled the same as the case when it
originates at the join.
Aggregation is performed incorrectly for JOIN queries
-----------------------------------------------------
Key: TEIID-4727
URL:
https://issues.jboss.org/browse/TEIID-4727
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.0.3
Environment: teiid-9.0.3 on WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final)
Reporter: dalex dalex
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 9.0.6, 9.2, 9.1.3
Aggregation is performed incorrectly for JOIN queries, like this
{code:sql}
select count(v2.b) from views.v1 right join views.v2 on true group by v1.b;
select count(v2.b) from views.v1 join (call procs.pr()) v2 on true group by v1.b;
select count(v2.b) from views.v1 left join (call procs.pr()) v2 on true group by v1.b;
select count(v2.b) from views.v1 right join (call procs.pr()) v2 on true group by v1.b;
{code}
showing as a result:
{code}
1
1
1
{code}
though these ones work correctly:
{code:sql}
select count(v2.b) from views.v1 join views.v2 on true group by v1.b;
select count(v2.b) from views.v1 left join views.v2 on true group by v1.b;
{code}
showing
{code}
1
1
2
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)