afs commented on issue #3535:
URL: https://github.com/apache/jena/issues/3535#issuecomment-3568186782
Thanks to @Aklakan, we now have fixes in the codebase.
One note : query 2 `SELECT * WHERE { ?s ?p ?o }` touches on an unrelated
issue.
1. It is stream-writing the results so it sends a 200 response then some
output, then later truncates the output at which point, it can not set the
right HTTP status code. Instead, it writes invalid syntax to the stream.
2. It may seem like the query cancellation isn't happening at the 1 second
mark. It is, for the query execution, but the HTTP/TCP connection output
buffers are full and this has to be written to the output. In HTTP/1.1 or
HTTP/2, the client has to read the response. If the client is slow, there can
be an appreciable delay to seeing the query finally completed and the time
logged. This is HTTP head-of-line blocking happening in the response direction
(it could be mitigated - at a performance cost - with some significant redesign
but not completely removed, because the HTTP connection is shared so the client
has to clear their end before it can be reused). HTTP/3 is different.
There will be a deployed development build with this in it in the next hour
or so (UTC: 19:00).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
