Bug 780981 (SOA-3452) - EDS Ingres as source - Query with LOCATE causing stackoverflow error
Summary: EDS Ingres as source - Query with LOCATE causing stackoverflow error
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3452
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.2.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0.ER5
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 16:52 UTC by Warren Gibson
Modified: 2011-10-21 14:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-21 14:37:44 UTC
Type: Bug


Attachments (Terms of Use)
stackoverflow.log (278.48 KB, text/plain)
2011-10-06 16:54 UTC, Warren Gibson
no flags Details
QT_Ingres10_Push.vdb (218.20 KB, application/octet-stream)
2011-10-06 16:54 UTC, Warren Gibson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3452 0 None None None Never
Red Hat Issue Tracker TEIID-1773 0 None None None Never

Description Warren Gibson 2011-10-06 16:52:24 UTC
project_key: SOA

EDS Query Testing is getting unexpected results on 16 queries involving LOCATE.  A couple examples queries are given below:

SELECT INTKEY, LOCATE(1, STRINGNUM) FROM BQT1.SmallA ORDER BY intkey  (Expected 50 records but received only 0)
Remote org.teiid.core.TeiidProcessingException: Source: null
see stackoverflow.log attached


SELECT INTKEY FROM BQT1.SmallA WHERE LOCATE(1, INTKEY) = 1 ORDER BY INTKEY
Remote org.teiid.core.TeiidProcessingException: Source: null
Is also a stackoverflow error.

Comment 1 Warren Gibson 2011-10-06 16:54:10 UTC
Attachment: Added: stackoverflow.log


Comment 2 Warren Gibson 2011-10-06 16:54:59 UTC
Attachment: Added: QT_Ingres10_Push.vdb


Comment 3 Van Halbert 2011-10-06 17:09:41 UTC
Link: Added: This issue Cloned to SOA-3455


Comment 5 Warren Gibson 2011-10-21 14:37:44 UTC
10/21/2011 - Tested ok.


Note You need to log in before you can comment on or make changes to this bug.