[
https://issues.jboss.org/browse/TEIID-2257?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2257.
-----------------------------------
Fix Version/s: 8.2
Resolution: Done
Added a ContinuousStatementCallback extension of StatementCallback with the method
beforeNextExecution that alerts the client the next execution is about to start. This is
not called until after the first execution. Also updated the reference.
The code relies on the assumption that continuous results must be forward-only and gets
slightly intrusive into the processing internals since we needed additional logic in
RequestWorkItem, BatchCollector, and TupleBatch. If we ever want to support remote
continuous clients that perform buffering, then additional work will be needed to preserve
the partial termination flags in the tuplebuffer.
Improved support for empty result sets in continuous executions
---------------------------------------------------------------
Key: TEIID-2257
URL:
https://issues.jboss.org/browse/TEIID-2257
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 8.2
When a continuous execution produces an empty result set, the execution will live forever
because the callback is never invoked.
For more details see:
https://community.jboss.org/message/763981#763981
--
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