Aklakan commented on issue #2881: URL: https://github.com/apache/jena/issues/2881#issuecomment-2525053814
> One thing to consider is invert the responsibilities have specific management of external resources - for example, add to a specific manager, one per query execution, pass in the context. End of execution clears up. This would also be good for per-execution caches. Maybe I am misunderstanding, how would that differ from the current design? Currently: 1. QueryIter registers itself at the execution context - the resource manager. 2. Something fails midway, resources are still tracked in the resource manager (although they could have been closed earlier). 3. End of execution closes all tracked resources - but warns because this shouldn't normally happen. -- 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]
