A GitHub issue with a minimal example query that reproduces the issue would be a good start so we can reproduce the issue and look into a fix
In workaround terms end users control their logging configuration so you could create a Log4j configuration that disables logging for the specific offending logger (assuming that this is a sufficiently specific logger to not suppress actually relevant logging) Rob From: Mikael Pesonen <[email protected]> Date: Tuesday, 28 March 2023 at 11:21 To: [email protected] <[email protected]> Subject: Strategies to avoid log flooding Hi, there are some cases where Jena generates dozens of gigs, maybe even terabytes, of log in one query. If you add a bad REGEX, it generates a long warning level exception for every row in db, or atleast million of them (disk filled up so don't know). Is there another way to avoid this except disable warnings?
