]
Steven Hawkins resolved TEIID-1681.
-----------------------------------
Resolution: Done
Thanks for catching this Gaurav. The limit node was being pushed too far, which caused
the projection logic to not correctly get the output elements.
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL:
https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
Labels: Limit
Fix For: 7.4.1
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: