Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/161
Sorry, I let this go without replying. No, the
`DatasetGraphTransaction.promotion` isn't really my concern. It's the fact that
you start a read transaction on a dataset, then try to write, and instead of
getting an exception, you get promoted. That seems a bit surprising and
dangerous to me. I'm not trying to block this, but wouldn't it be possible to
add a new value for `ReadWrite` now instead of after the fact? Old code could
just ignore it and new code could check for it to see if promotion is enabled
for the given transaction.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
