[
https://issues.jboss.org/browse/TEIID-2676?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-2676:
--------------------------------------
Your code only produces an initial delay, as no DNA will be thrown
after that.
Then I must not understand something. It's my understanding that
since the execution is not reusable, a new instance is created when the command is
reexecuted. This effectively resets the letExecutionContinue to false each time the
command is (re)executed so I would expect a delay.
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 there's only one execution in my test case, again, I would expect the
delay on every execution, no?
Further, I don't understand why the behavior should be different when forkable is true
versus false.
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