Continuous Executions - Join doesn't seem to honor NO_POLLING

markaddleman Sep 11, 2013 8:21 PM

I've got two queries each run in continuous mode going to the same translator: SELECT * FROM T1 and SELECT * FROM T1 CROSS JOIN T2. The translator throws NO_POLLING on execute() and waits for an event on a bus before it calls executionContext.dataAvailable(). The query without the join works fine. When processing the query with the join, the engine doesn't honor the NO_POLLING.

Attached is a test case.

testcase.zip 37.0 KB

1. Re: Continuous Executions - Join doesn't seem to honor NO_POLLING

shawkins Sep 11, 2013 10:45 PM (in response to markaddleman)

Check the javadoc for no_polling - it is specifically referring to the notion of a time based poll. The plan continuing to process because of other source events is not considered a polling event. You'd have to use a DataNotAvailableException with the strict flag set to true to prevent the source from being asked entirely.
Actions
2. Re: Continuous Executions - Join doesn't seem to honor NO_POLLING

markaddleman Sep 11, 2013 11:20 PM (in response to shawkins)

Ah, of course. For some reason, setStrict had slipped my mind. Thanks
Actions

Go to original post