Github user afs commented on the issue:
https://github.com/apache/jena/pull/161
Let's get this into the codebase first (inactive). JENA-1222 and JENA-1224
are both changes to TDB's ``TransactionManager`` and juggling multiple branches
of nearby code changes is not nice.
I've tried to write a test for snapshot isolation promotion but it relies
on a thread pause which elsewhere has been unstable on a heavily loaded CI
server (`TestTransPromote.promote_clash_active_writer`). At the moment, there
is no special code for the "active writer then abort" case. It may be possible
but if it looks like a major change to TDB1, then it may not be worth and may
be a sign that the specific feature is generally something that warps the rest
of the system.
Until we get the contract details settled, changing TIM seems premature.
---
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.
---
