[
https://issues.apache.org/jira/browse/DRILL-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180764#comment-14180764
]
Parth Chandra commented on DRILL-1568:
--------------------------------------
To handle this case, the client lib will have to keep the query id around till
the results are all consumed and I think the id should be cleared when a query
completed status is returned (I think this is part of the problem we appear to
get 'spurious' messages from the server).
We could also just silently throw away any results that we get back from the
server for which we do not have a corresponding query id.
The thing to watch out for during cancellation is the m_pendingRequests
counter. If the counter is decremented incorrectly, the client will hang.
I'll take a stab at this (real soon now)
> Cancel request to server should cancel all futher results from coming back
> --------------------------------------------------------------------------
>
> Key: DRILL-1568
> URL: https://issues.apache.org/jira/browse/DRILL-1568
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - C++
> Reporter: Norris Lee
>
> When a cancel request is sent to the server, results that have already been
> processed still get returned to the client. This throws a query out of order
> error in the the C++ client since the query id mapping has already been
> deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
