[teiid-issues] [JBoss JIRA] Resolved: (TEIID-1389) Add additional detection for conflicting criteria to help optimize query plan

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-1389.
-----------------------------------

    Fix Version/s: 7.3
       Resolution: Done


Added optimization in the rewriter for in, is null, and comparison criteria.  It is not exhaustive.  It tends to only examine situations involving constants (e.g. x in (1,2), x < 5, etc.) and only when the predicates are conjuncts.  So the example in this issues using 'OR' would be optimized.  It should instead be entered as an IN predicate.

> Add additional detection for conflicting criteria to help optimize query plan
> -----------------------------------------------------------------------------
>
>                 Key: TEIID-1389
>                 URL: https://issues.jboss.org/browse/TEIID-1389
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>    Affects Versions: 6.0.0
>            Reporter: Marc Shirley
>            Assignee: Steven Hawkins
>             Fix For: 7.3
>
>
> Add additional detection for conflicting criteria such as "(column1=1 OR column1=2) AND column1=3".  The attempted use case was a case of a UNION that was using the column as a measure of selecting a specific datasource, with each query joined by the UNION having a specific set of column1 values (such as "column1=1 OR column1=2").  In the case of the end user application submitting criteria such as "column1=3", the query planner should prune any branches of the UNION with a conflicting set of values for column1.  It would also be helpful if other operators such as <, >, <>, IN, etc. could be accounted for.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira