[
https://issues.apache.org/jira/browse/JENA-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636292#comment-13636292
]
Andy Seaborne edited comment on JENA-440 at 4/19/13 2:48 PM:
-------------------------------------------------------------
This is nothing to do with connections where there are other issues.
e.g. CONNECTION_TIMEOUT is to to establish a connection so isn't relevant.
It is about timeouts on query execution within ARQ and meeting the contract
See QueryExecutionBase#setTimeout javadoc.
The supposed contract is N,M - time to first result and time to last result.
One consideration for more complicated models is the cost - a query may be
yielding results from very cheap-to-execute patterns. A per row cost could
lead to overhead.
was (Author: andy.seaborne):
This is nothing to do with connections where there are other issues.
e.g. CONNECTION_TIMEOUT is to to establish a connection so isn't relevant.
It is about timeouts on query execution within ARQ and meeting the contract
See QueryExecutionBase#setTimeout javadoc.
The supposed contract is N,M - time to first result and time to last result.
This is fairly conventional.
> Query timeout does not always correctly move to the second query timeout
> after first row yielded
> ------------------------------------------------------------------------------------------------
>
> Key: JENA-440
> URL: https://issues.apache.org/jira/browse/JENA-440
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.10.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
--
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
