[
https://issues.jboss.org/browse/TEIID-1968?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1968.
-----------------------------------
Fix Version/s: 7.7.1
8.0
Resolution: Done
Fixed the issue by updating the correlated references appropriately in the
RelationalPlanner. This is a regression caused by the change to a generated aggregate
view.
Also improved validation to ensure that only grouping columns may be used as correlated
reference when a group by is used. That appeared to have been previously missed.
Note that the issue TEIID-1680 still exists which requires a workaround if aggregate
expressions are used as correlated references.
NPE in GoupingNod
-----------------
Key: TEIID-1968
URL:
https://issues.jboss.org/browse/TEIID-1968
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 7.7.1, 8.0
Attachments: teiid-npe.txt
I get an NPE within Teiid's GroupingNode.initialize when executing the following SQL
SELECT XMLELEMENT(NAME metadata,
XMLFOREST(objectName as objectName),
(SELECT XMLAGG(XMLELEMENT(name subTypes,
XMLFOREST(subType)))
FROM chorus_metadata.property_filtered b
WHERE a.objectName=b.objectName
GROUP BY subType)
)
FROM chorus_metadata.property_filtered a
GROUP BY objectName
LIMIT 1
chorus_metadata.property_filtered is an internal materialized view.
--
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