Github user afs commented on the issue:
https://github.com/apache/jena/pull/161
To track whether a promotion is possible for fully serialized, the code now
checks a version number. The necessary information is available elsewhere
(whether a new transaction would see the same dataset a
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/161
So ideally, it would be another writer _committing_ that would throw a
switch to refuse promotion to extant transactions? Instead of another writer
simple existing?
---
If your project is set up for i
Github user afs commented on the issue:
https://github.com/apache/jena/pull/161
Yes.
---
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 e
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/161
I guess I'm confused as to why one can't determine (from the version
numbers) whether another transaction has committed? If you know a transaction's
version number and you know the transaction manager's
Github user afs commented on the issue:
https://github.com/apache/jena/pull/161
Version number only tell you about the past (see
``TransactionManager.notifyCommit`` where the version number increases - this
is as the writer finishes up).
When a writer is active and has not co
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/161
Oh, okay, I get it now. And even if you could block, as you wrote above,
that could be a really long time in some cases. Do you want me to write
something for TIM to bring a version number to the dataset
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
[
https://issues.apache.org/jira/browse/JENA-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420468#comment-15420468
]
ASF GitHub Bot commented on JENA-1222:
--
Github user afs commented on the issue:
h
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/161
Okay, I'll hang tight.
---
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
