[
https://issues.redhat.com/browse/TEIID-5994?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-5994.
-----------------------------------
Resolution: Done
Addressed in master just for the narrow case of the must pushdown function. There are
likely other similar scenarios where we may be masking a capabilities/connection issue
with a planning exception - if we encounter those we can either add this check to those
places or look toward adding a general check via catching query planner exceptions.
However the latter seems like it wouldn't work unless we start associating the
originating model (if applicable) with the exception.
If capabilities are not available not pushing a function masks the
problem
--------------------------------------------------------------------------
Key: TEIID-5994
URL:
https://issues.redhat.com/browse/TEIID-5994
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 15.0
Original Estimate: 1 hour
Remaining Estimate: 1 hour
In a situation that requires subexpression pushing, for example:
select virtual_func(source_func(col)) from tbl
such that source_func must be pushed. The actual exception will be about the expression
not being able to be pushed, and not about the capabilities being unavailable - which
could only be seen at a debug level.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)