[
https://issues.jboss.org/browse/TEIID-3295?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-3295.
-----------------------------------
Resolution: Done
Updated the default to true. Also updated the hint logic to support the subquery hints in
all locations. In some circumstances this can produce an undesirable plan. For example
when the main part of the query needs sorting for join processing, or few subqueries will
actually run - in these specific circumstances now that we have an enhanced join or
minimal cardinality would indicate result in a similar or better plan with the join
unnested. In general users can choose to use the no_unnest hint, but ideally we'll
capture any deficiencies in the logic - which may perhaps necessitate speculative
planning.
Change subqueryUnnestDefault to true
------------------------------------
Key: TEIID-3295
URL:
https://issues.jboss.org/browse/TEIID-3295
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.10
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.10
Since TEIID-2149 the scope of the property has been limited in scope and should be
flipped to true to allow for more efficient planning. In the worst case users can use the
NO_UNNEST hint to prevent the optimization.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)