[
https://issues.jboss.org/browse/TEIID-2676?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2676:
---------------------------------------
I get a barrage of "Row received" with no delay. I'm
running an JDK "1.7.0_11-b21" on an 8 core laptop.
Your code only produces an initial delay, as no DNA will be thrown after that.
I don't have time to come with a test case now but it seems the
misbehavior is also tied to the complexity of the query - adding a join can trigger the
bug regardless of the forkable setting.
Here again it may the the non-strict nature that is throwing things off. When any source
reports that data is available the engine resumes the plan - but doesn't specifically
know/care that it was data source x that's now ready. Since it is restarting it will
go through the default processing logic that can result in polls against all sources and
without a strict DNA you won't see a pause.
Delay in DataNotAvailableException not honored when isForkable=false
--------------------------------------------------------------------
Key: TEIID-2676
URL:
https://issues.jboss.org/browse/TEIID-2676
Project: Teiid
Issue Type: Bug
Reporter: Mark Addleman
Assignee: Steven Hawkins
Attachments: DelayNotHonored.java
It appears that when isForkable=false, the delay specified in DataNotFoundException is
not honored. I have seen similar behavior even when isForkable=true but it's a
Heisenbug: when I add logging, it goes away. It smells like a race condition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira