Aklakan commented on issue #2701: URL: https://github.com/apache/jena/issues/2701#issuecomment-4205711067
For the time being, I have factored out the execution tracking as a separate maven dep and a stand-alone Fuseki drop-in plugin jar. https://github.com/Scaseco/jena-exectracker > ## ⚠️ Limitations > The tracker will be notified of all query and update execution requests, however there are limitations on the information that can be extracted: > * Any query will appear in its SELECT form. This is because QueryEngineRegistry operates on a lower level than CONSTRUCT, DESCRIBE and ASK. > * Update requests only appear as generic # Update Request. This is because the UpdateEngineRegistry only receives notification of update requests, but not the SPARQL statement. https://github.com/Scaseco/jena-exectracker/issues/1 - for the first limitation, it should be possible to just rely on `ARQConstants.sysCurrentQuery` for the second, perhaps all that's needed is an analogous `ARQConstants.sysCurrentUpdate`. If it's ok, I would close the PR proposals #3184 #3511 #3818. It seems better to go back to the drawing board - i.e. issue page rather than PR on how to best proceed. -- 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]
