[GitHub] jena pull request #161: Plain begin - read transactions promoting to write t...

Github user afs closed the pull request at: https://github.com/apache/jena/pull/161 --- 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 b

[GitHub] jena issue #161: Plain begin - read transactions promoting to write transact...

Github user afs commented on the issue: https://github.com/apache/jena/pull/161 Proposal: the default behaviour is "no read commited" for `begin()` (behavior 2 in the description) with an option to call `setReadCommited` (or some such name). And/or a `readCurrent` which effectively re

[GitHub] jena issue #161: Plain begin - read transactions promoting to write transact...

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/161 I like the proposal, basically, although I suspect it might be a little tricky to do the original suggestion of "limited read committed" in current TIM. Adding `readCurrent` would make seem to make that

[jira] [Created] (JENA-1222) Control the flushing of the commit log based on journal size.

Andy Seaborne created JENA-1222: --- Summary: Control the flushing of the commit log based on journal size. Key: JENA-1222 URL: https://issues.apache.org/jira/browse/JENA-1222 Project: Apache Jena