[
https://issues.jboss.org/browse/TEIID-5374?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-5374:
----------------------------------
Description:
A simple structure like:
{code}
join
access
union
access
access
{code}
will reject creating a cost based dependent join over the union if the number of
independent values seems too large for a virtual dependent join.
A related issue is that TEIID-5020 introduced a regression when creating a dependent join
that is eventually pushed over a union below an access node:
{code}
dependent select
access
set op
..
{code}
the logic attempts to move nested dependent select back above the access node - so that
only a single dependent predicate exists - based upon the node that is created at a child.
However if the child projects a literal into the dependent set criteria, then the result
is invalid.
was:
A simple structure like:
join
access
union
access
access
will reject creating a cost based dependent join over the union if the number of
independent values seems too large for a virtual dependent join.
Allow for non-virtual dependent joins to be created over unions
----------------------------------------------------------------
Key: TEIID-5374
URL:
https://issues.jboss.org/browse/TEIID-5374
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.0
A simple structure like:
{code}
join
access
union
access
access
{code}
will reject creating a cost based dependent join over the union if the number of
independent values seems too large for a virtual dependent join.
A related issue is that TEIID-5020 introduced a regression when creating a dependent join
that is eventually pushed over a union below an access node:
{code}
dependent select
access
set op
..
{code}
the logic attempts to move nested dependent select back above the access node - so that
only a single dependent predicate exists - based upon the node that is created at a child.
However if the child projects a literal into the dependent set criteria, then the result
is invalid.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)