[
https://jira.jboss.org/jira/browse/TEIID-216?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-216.
----------------------------------
Resolution: Deferred
Marking as deferred. Zero sized batch processing is a very minor issue, once a timeout or
cancel has been issued the current plan will typically fail-fast. Also we will now get
immediate notification of a failing client connection, or at the very least a ping timeout
that will cause a cancel. Until we clients accessing through a non-Java interface
it's not imperative to move/duplicate the timeout handling on the server.
Query timeout should be enforced by the server
----------------------------------------------
Key: TEIID-216
URL:
https://jira.jboss.org/jira/browse/TEIID-216
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Fix For: 6.3
Defect Tracker #4990 : Query timeouts should be enforced by the server and client.
Also the RelationalNode nextbatch method will need to be made aware of the
timeslice/timeout when handling 0 length batches.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira