[
https://issues.jboss.org/browse/TEIID-1773?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1773.
-----------------------------------
Fix Version/s: 7.4.1
7.6
Resolution: Done
The locate modifier was returning a new locate function which the logic attempts to
translate again, thus the stack overflow.
Our translation logic allows for passing back expressions that will be further modified,
which means that when a non-null list is returned by a modifier we attempt to translate
those results. We also maintain a identity map to guard against situations where the
original object is passed back by the translator.
Ingres as source - Query with LOCATE causing stackoverflow error
----------------------------------------------------------------
Key: TEIID-1773
URL:
https://issues.jboss.org/browse/TEIID-1773
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 7.4.1
Reporter: Warren Gibson
Assignee: Steven Hawkins
Fix For: 7.4.1, 7.6
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira