[teiid-issues] [JBoss JIRA] (TEIID-2068) Recursion Limit not being processed for XML documents - Possible recursion issue?
[
https://issues.jboss.org/browse/TEIID-2068?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2068:
---------------------------------------
The command log isn't so much troubling as it indicates the need for a staging table
and or a mat view.
What does your last comment mean? If you set the limit to 10 you are getting valid
results back to a depth of 10? Does this contradict the test expectations and/or your
initial description in which you expected only to a depth of 4?
In re-inspecting RecuseProgramCondition, I think that the logic is actually fine. Other
than the record feature not being implemented it looks like you may not have a good set of
test expectations and/or a poorly performing query that gets worse at further recursion
depths.
Recursion Limit not being processed for XML documents - Possible
recursion issue?
---------------------------------------------------------------------------------
Key: TEIID-2068
URL: https://issues.jboss.org/browse/TEIID-2068
Project: Teiid
Issue Type: Bug
Components: Query Engine
Environment: SOA-P 5.3 ER3
Reporter: Paul Nittel
Assignee: Steven Hawkins
Attachments: RecursionLimit_MPS.zip, server.log, teiid-command.log.8
I ran the E2ERecursiveXmlTextSource test. It involves setting a limit of 3 on the
recursion, and then changing the limit to 4 (where all XML document queries will pass). I
found the limit exception was being thrown regardless of the setting (even up to 10).
I changed the behavior from THROW to RECORD and now the queries do not return (in a
timely manner), leading me to worry that recursion may be the cause, not the limit
itself.
Model Project Set and server log will be attached.
Just looked at the command log and it looks pretty weird. I'd be inclined to start
there. I AM able to successfully query the source (text).
--
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