[
https://issues.jboss.org/browse/TEIID-2939?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2939:
----------------------------------
Description:
If a view over a left outer join has a row condition and is used in a simple aggregation:
select count\(*) from vw
Then a null pointer exception will occur when considering optional joins.
If intervening criteria is added:
select count\(*) from vw where ...
we can get past the initial error, but will fail in initializing the join node with an
assertion error. Both of these have the same root issue, which is our attempt to make the
logic selective about when assign output elements is run, which leads to the output
elements not being in place when later needed.
was:
If a view over a left outer join has a row condition and is used in a simple aggregation:
select count(*) from vw
Then a null pointer exception will occur when considering optional joins.
If intervening criteria is added:
select count(*) from vw where ...
we can get past the initial error, but will fail in initializing the join node with an
assertion error. Both of these have the same root issue, which is our attempt to make the
logic selective about when assign output elements is run, which leads to the output
elements not being in place when later needed.
Issues with applying row based security
---------------------------------------
Key: TEIID-2939
URL:
https://issues.jboss.org/browse/TEIID-2939
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
If a view over a left outer join has a row condition and is used in a simple
aggregation:
select count\(*) from vw
Then a null pointer exception will occur when considering optional joins.
If intervening criteria is added:
select count\(*) from vw where ...
we can get past the initial error, but will fail in initializing the join node with an
assertion error. Both of these have the same root issue, which is our attempt to make the
logic selective about when assign output elements is run, which leads to the output
elements not being in place when later needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira