[TEIID-4144] Mismanagement of output columns in ruleimplementjoinstrategy Created: 15/Apr/16  Updated: 24/Aug/16  Resolved: 15/Apr/16

Status: Closed
Project: Teiid
Component/s: Query Engine
Affects Version/s: 9.0, 8.12.5, 8.13.1, 8.7.3.6_2
Fix Version/s: 9.0, 8.12.5, 8.7.6.6_2, 8.13.4

Type: Bug Priority: Major
Reporter: Steven Hawkins Assignee: Steven Hawkins
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1327612
Bugzilla Update:
Perform

 Description   

Related to TEIID-3973 - the fix introduced a situation where if the sort node is not added and a join expression is used and there are intervening nodes, then the output columns are not correctly managed. The result is a similar value not found exception.



 Comments   
Comment by Steven Hawkins [ 15/Apr/16 ]

Switched the project to be added as a parent of the source node - which is the logical point where the sort is inserted and the output columns are being manipulated.

Generated at Fri Nov 16 03:41:36 EST 2018 using Jira 7.12.1#712002-sha1:609a50578ba6bc73dbf8b05dddd7c04a04b6807c.