Aklakan commented on issue #3535: URL: https://github.com/apache/jena/issues/3535#issuecomment-3490727299
@afs Are there arguments against checking `Thread.interrupted()` in the iterators returned by `graph.find()` (or more generally the whole `Iter` machinery) so that async abort would not require an execution context? Also, it would work naturally with conventional blocking IO - such as when used in custom (property) functions. Conversely, perhaps this would be the way to solve these abort issues once and for all? This check would have to go to the hasNext/next and also all overriden forEachRemaining methods. In one of my earlier PRs I added the interrupted check to `QueryIteratorBase` - but this does not affect the lower-lever iterators. -- 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]
