[
https://issues.jboss.org/browse/TEIID-4943?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-4943:
----------------------------------
Description:
When an inner join with a predicate that can be copied is pushed, we will still create the
copied criteria. In some situations, this over-constraining is not desirable. We should
minimize when this occurs. For example:
select col1 from t1, t2 where t1.col = t2.col and t1.col = 1
should pushdown as:
select col1 from t1, t2 where t1.col = t2.col and t1.col = 1
not:
select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 and t2.col = 1
was:When an inner join with a predicate that can be copied is pushed, we will still
create the copied criteria. In some situations, this over-constraining is not desirable.
There should be a capability to determine if this copying should take place.
Summary: Minimize creating redundant copied predicates (was: Allow translators to
declare if copied criteria should be included)
Minimize creating redundant copied predicates
---------------------------------------------
Key: TEIID-4943
URL:
https://issues.jboss.org/browse/TEIID-4943
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0
When an inner join with a predicate that can be copied is pushed, we will still create
the copied criteria. In some situations, this over-constraining is not desirable. We
should minimize when this occurs. For example:
select col1 from t1, t2 where t1.col = t2.col and t1.col = 1
should pushdown as:
select col1 from t1, t2 where t1.col = t2.col and t1.col = 1
not:
select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 and t2.col = 1
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)