Thank you for your response, Andy. I wouldn’t expect the full update to be logged, although I am curious how the verbose mode can be switched on. I think a summary, on the lines of how SPARQL queries are logged with just the query itself.
I will submit an issue for review. Thanks again -- Scott From: Andy Seaborne <[email protected]> Sent: Thursday, August 29, 2024 8:25 AM To: [email protected] Subject: Re: [EXTERNAL] Re: Configuring logging in Fuseki CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Scott, They are not logged normally - they are in verbose mode. There are some issues with logging them due to scaling issues. * Update can be very large * Update request are streamed Because of streaming, the whole text is not available at the point of logging (at the operation start). An update request can be many operations and each operation is executed (but not committed) before the next one is read and processed. Something like: INSERT DATA { .... } ; INSERT DATA { .... } ; DELETE DATA { .... } ; INSERT DATA { .... } ; Adding large amounts of data is often better done by POSTing RDF. RDF patch can be better, but not a standard, for a mix of adds and deletes. Maybe the use of "small updates" dominates usage and could be logged. Do you want the whole update logged or would a summary be sufficient? Please do raise a issue at https://github.com/apache/jena/issues<https://github.com/apache/jena/issues> and we can gather input. Andy On 28/08/2024 21:41, Scott Henninger wrote: > That works nicely, thank you for the worked out example, Øyvind. > > A follow-up question. I noticed that queries are logged, but not updates > (i.e. SPARQL update). Is there a logger configuration specifically for > updates? Logging queries is fine but I’d also like to know when and how my > data is updated. > > Thanks in advance, > -- Scott
