]
Steven Hawkins commented on TEIID-5434:
---------------------------------------
The issue is with the sort optimization that is pulling up the distinct operation on the
union to the join node. The intervening select node is having it's output columns
left as the reduced set, so that when the distinct is processed it's over just the
join predicate column. That is why you are seeing a smaller row count with the count
query. I'll have a fix for this today.
count(*) returns different nr of rows compared to normal select
---------------------------------------------------------------
Key: TEIID-5434
URL:
https://issues.jboss.org/browse/TEIID-5434
Project: Teiid
Issue Type: Bug
Affects Versions: 10.3.3
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Priority: Critical
Attachments: count_plan.txt, count_plan_debug_log.txt, count_plan_text.txt,
select_plan.txt, select_plan_debug_log.txt, select_plan_text.txt
Normal select return 162175 rows:
{code:sql}
select pa.ICUSessionID,11074, obr.DateTime, obr.varvalue, true, 15001866
from tv_retrieve_observrec obr
join kd_matric.ExtrPatICUAdmissions epa on epa.PatientID = obr.admissionid
join kd_matric.PatICUAdmissions pa on pa.ICUSessionID = epa.ICUSessionID and pa.BatchID
< 1152
where obr.VariableID = 15001866;
{code}
count query return a count of 11573
{code:sql}
select count(*)
from tv_retrieve_observrec obr
join kd_matric.ExtrPatICUAdmissions epa on epa.PatientID = obr.admissionid
join kd_matric.PatICUAdmissions pa on pa.ICUSessionID = epa.ICUSessionID and pa.BatchID
< 1152
where obr.VariableID = 15001866;
{code}
This was detected on a snapshot release of 10.3.3