[
https://issues.jboss.org/browse/TEIID-1777?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1777.
-----------------------------------
Resolution: Deferred
Ah I misread. Ingres does indeed return the wrong result. They cannot handle nested
aggregates. A new capability would be needed to workaround their limitation.
Starting with Teiid 7.5 I believe that we'll detect that query 2 must return a count
of 1 regardless.
Given that these are uncommon scenarios, at this point I'll resolve as deferred, but
we can workaround by inhibiting pushdown if a customer needs it.
Ingres as source - 3 VQT Queries using COUNT(*) returning unexpected
results
----------------------------------------------------------------------------
Key: TEIID-1777
URL:
https://issues.jboss.org/browse/TEIID-1777
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 7.4.1
Reporter: Warren Gibson
Assignee: Steven Hawkins
EDS Query Testing is getting unexpected results on the following queries:
3 queries involving COUNT(*)
QUERY: SELECT COUNT(*) FROM VQT.Agg1
COMMENT: Expected count of 47 rows but got count of 1.
Agg1 transformation: SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA GROUP BY
BQT1.SmallA.StringNum
QUERY: SELECT COUNT(*) FROM VQT.Agg3
COMMENT: Expected count of 1 but got count of 50.
Agg3 transformation: SELECT COUNT(*) FROM BQT1.SmallA
QUERY: SELECT COUNT(*) FROM VQT.Agg4
COMMENT: Expected count of 47 but got count of 1.
Agg4 transformation: SELECT MIN(BQT1.SmallA.StringNum),
SUM(BQT1.SmallA.IntKey), AVG(BQT1.SmallA.IntKey) FROM BQT1.SmallA GROUP BY
BQT1.SmallA.StringNum
--
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