From: <tr...@do...> - 2014-02-20 15:50:54
|
<p>A new comment has been added to the following issue.</p> <table border="0"> <tr> <td width="90px" valign="top"><b>Title:</b></td> <td>Cannot increase query timeout more than default HttpWebRequest 100 seconds for SPARQL Update on Stardog</td> </tr> <tr> <td><b>Project:</b></td> <td>Core Library (dotNetRDF.dll)</td> </tr> <tr> <td><b>Created By:</b></td> <td>Rob Vesse</td> </tr> <tr> <td><b>Date:</b></td> <td>2014-02-20 03:50 PM</td> </tr> <tr> <td><b>Comment:</b></td> </tr> <tr> <td colspan="2"><p> I don't believe we currently provide any mechanism for controlling the HTTP timeouts for Storage Providers. Options.QueryExecutionTimeout both refer specifically to in-memory execution though could be used as a default value for HTTP timeouts once added.</p> <p> This should be relatively easy to implement and I will get this into the next release</p></td> </tr> </table> <p> More information on this issue can be found at <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400</a></p> <p style="text-align:center;font-size:8pt;padding:5px;"> If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options. </p> |