[ 
https://issues.apache.org/jira/browse/DRILL-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076481#comment-14076481
 ] 

Xiao Meng commented on DRILL-1197:
----------------------------------

Hi Parth, my apply order is [#DRILL-1027], [#DRILL-1137] then this patch. I am 
working on integrate [#DRILL-998] since I omitted this one earlier:( For the 
cancel operation, it is because I cannot run it on win32 build setting, x64 
works fine though. It seems not a portable solution as stated in the boost 
document 

[http://www.boost.org/doc/libs/1_54_0/doc/html/boost_asio/reference/basic_stream_socket/cancel/overload1.html]

{quote}
For portable cancellation, consider using one of the following alternatives:

- Disable asio's I/O completion port backend by defining 
BOOST_ASIO_DISABLE_IOCP.
- Use the close() function to simultaneously cancel the outstanding operations 
and close the socket.
When running on Windows Vista, Windows Server 2008, and later, the CancelIoEx 
function is always used. This function does not have the problems described 
above.
{quote}

The first solution does not work for me (use BOOST_ASIO_DISABLE_IOCP). I tested 
the second one and shutdown socket is good enough to cancel operations and 
single error. (Use socket close operation in handleHandshakeTimeout will 
trigger handleRead and singal additional error and problematic in the ODBC 
driver).

> C++ Client.  Differentiate socket/handshake/query timeout for deadline timer.
> -----------------------------------------------------------------------------
>
>                 Key: DRILL-1197
>                 URL: https://issues.apache.org/jira/browse/DRILL-1197
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Client - C++
>            Reporter: Xiao Meng
>            Assignee: Xiao Meng
>             Fix For: 0.5.0
>
>         Attachments: DRILL-1197.1.patch.txt
>
>
> [#DRILL-852] introduced deadline timer to C++ Client. It use a global setting 
> of timeout for all reading operation. We should differentiate timeout for 
> different operations and also populate the status to client library user.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to