[
https://issues.apache.org/jira/browse/JENA-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918143#comment-16918143
]
Andy Seaborne commented on JENA-1731:
-------------------------------------
The timeout example is for a SPARQL query. This is the existing way to set a
timeout.
This does not apply to text search directly - but if the query goes over the
limit it will abort the text search when the SPARQL engine gets the chance.
The query exits with a "QueryCancelledException" which Fuseki tries to send
back to the client.
Unfortunately, in HTTP, the response code is sent back first. So it is possible
that the client can get the 200, then the result stream is truncated. Fuseki
writes syntactically illegal results to force an error processing the results.
This is something SPARQL 1.2 CG may address. There are several issues that
touch on this known problem.
To continue this discussion, the users@ list would be a good place.
> Improve Fuseki service endpoint configuration
> ---------------------------------------------
>
> Key: JENA-1731
> URL: https://issues.apache.org/jira/browse/JENA-1731
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Jena 3.13.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is a follow-on JIRA from JENA-1715.
> A sketch for new configuration description for a service endpoint:
> {noformat}
> <#service> rdf:type fuseki:Service ;
> fuseki:name "/ds" ;
> fuseki:endpoint [
> fuseki:operation fuseki:Query ;
> fuseki:allowedUsers (....) ;
> fuseki:timeout "1000,10000" ;
> fuseki:queryLimit 1000;
> arq:unionGraph true;
> ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "1000,10000"
> ] ;
> ] ;
> fuseki:endpoint [
> fuseki:name "sparql" ; ## becomes "/ds/sparql"
> fuseki:operation fuseki:Query ;
> ...
> ] ;
> fuseki:endpoint [
> fuseki:name "sparql" ;
> fuseki:operation fuseki:Update ;
> ...
> ] ;
> .
> {noformat}
> with the goal of being able to have new operations confiugured into the
> Fuseki endgine, and not the fixed set of operations as is currently with
> {{fuseki;service*}}.
> For example: a "patch" service - POST an [RDF
> Patch|https://afs.github.io/rdf-delta/rdf-patch.html] or have a data
> validation service for SHACL etc.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
