[
https://issues.redhat.com/browse/TEIID-5922?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-5922.
-----------------------------------
Fix Version/s: (was: 13.0.3)
Resolution: Done
This turned out to be very straight-forward, only requiring a null check. Generally we
haven't seen it in other cases because other subqueries would be immediately
recognized as unmergable - otherwise we'd have hit the same exception.
NPE in simple select with procedure subquery
--------------------------------------------
Key: TEIID-5922
URL:
https://issues.redhat.com/browse/TEIID-5922
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 14.0, 13.1.1
Original Estimate: 4 hours
Time Spent: 1 hour, 30 minutes
Remaining Estimate: 2 hours, 30 minutes
A query in the form of:
SELECT (call proc())
is resulting in an npe:
{code}
java.lang.NullPointerException
at
org.teiid.query.optimizer.relational.rules.RulePlanSubqueries.planMergeJoin(RulePlanSubqueries.java:272)
at
org.teiid.query.optimizer.relational.rules.RulePlanSubqueries.processSubqueries(RulePlanSubqueries.java:232)
at
org.teiid.query.optimizer.relational.rules.RulePlanSubqueries.execute(RulePlanSubqueries.java:193)
at
org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:1101)
{code}
Until relatively recently we disallowed queries from having subqueries if there was no
from clause. That change was checked against regular subqueries, but apparently not
procedure subqueries.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)