[
https://issues.apache.org/jira/browse/JENA-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235868#comment-16235868
]
A. Soroka commented on JENA-1412:
---------------------------------
Small thing, but I think this could be a subclass of
{{QueryCancelledException}}, or even better {{QueryCancelledException}} and a
new {{Exception}} should both inherit from some supertype. We now throw
{{QueryCancelledException}} when a client cancels out of a query, and this
(current) situation is when the _server_ cancels the client out of a query. I
think that's enough of a difference to merit a different type.
I think that currently the timeout functionality for queries over HTTP actually
gets offloaded onto the HTTP client in use:
https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/sparql/engine/http/QueryEngineHTTP.java#L632
whereas for local queries we run the clock ourselves... we can't really ask the
HTTP client to count results (or at least not in any sane way I can see) so
maybe we want to stop asking it to time the timeouts just to keep everything
running the same way? I dunno...
> Allow query results to be limited
> ---------------------------------
>
> Key: JENA-1412
> URL: https://issues.apache.org/jira/browse/JENA-1412
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ, Fuseki
> Affects Versions: Jena 3.5.0
> Reporter: Andy Seaborne
> Priority: Major
>
> In the same style as query timeout, have the engine limit the total results
> returned.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
