[teiid-issues] [JBoss JIRA] Updated: (TEIID-1528) ruleimplementjoin strategy may generate an order by that does not use a relevant index

[Steven Hawkins (JIRA)]

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

Steven Hawkins updated TEIID-1528:
----------------------------------


The fix in 7.4 will cause non key covering equi-join predicates to not be used.  This could lead to the wrong results in non-dependent joins or multiple-dependent query composite value dependent joins.

E.g.

create local temporary table x (e1 string, e2 integer, primary key (e1));
create local temporary table x1 (e1 string, e2 integer, primary key (e1));
...
select x.e1 from x, x1 where x.e2 = x1.e2 and x.e1 = x1.e1; -- can produce the wrong results because x.e2 = x.e1 will be ignored.

> ruleimplementjoin strategy may generate an order by that does not use a relevant index
> --------------------------------------------------------------------------------------
>
>                 Key: TEIID-1528
>                 URL: https://issues.jboss.org/browse/TEIID-1528
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 6.0.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 7.4
>
>
> If a table is given additional join criteria not covered by an index or if a composite key is being used ruleimplementjoinstrategy may - either add an item not covered by the index to the order by or not use the proper order of the index columns.

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