Github user ehedgehog commented on the issue:
https://github.com/apache/jena/pull/157
I don't see that an AtomicBoolean has any advantage over a volatile
variable in this code. The only changes made are setting `cancelled` (the
volatile boolean) from `false` (initial value) to `true` when `cancel()` is
called. Once it's true it stays true. And the only place it is written to and
read from from is within AbortableComparator itself.
Is volatile perhaps not noisy enough to trigger a reader's notice?
Chris
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
