OK - so no block on a 2.12.0 release. Cool.
(2) is definitely a "big thing" as it'll break existing app code.
Off the top of my head, sorting out the models-across-transaction
boundaries is going to be related.
It might be better to do together with all datasets being transactional.
There are two general schemes that can be used for places where
transactionality needs to be externally applied (e.g. in-memory): either
RDF patches, which are reversible for abort(), or a MRSW locking. Fuseki
uses the latter currently unless it's a TDB dataset.
Andy
On 24/07/14 14:13, Rob Vesse wrote:
The LocationLock functionality is now enabled and working. I have also
updated the staging documentation to reference this new functionality.
I haven't closed JENA-648 as the description talks about two things:
1 - LocationLock
2 - Transactions on by default + upgradeable transactions
Probably what needs to be done is a new JIRA filed for 2 which references
back to the current JIRA and then JENA-648 can be resolved and closed
The only other thing I wanted to do is send a message to the developer
list to ask for people to test snapshots
Rob
On 24/07/2014 13:32, "Andy Seaborne" <[email protected]> wrote:
On 22/07/14 10:19, Rob Vesse wrote:
+1
Yes I think we are probably about ready
I would like to get JENA-648 (TDB LocationLock's) enabled, thanks for
spotting and fixing the cause of the Windows failures. I will enable
that
shortly and make sure everything builds nicely now
Is that OK now? It looks like from JIRA but is it open still so I was
wondering if there is still work to do. Anything I can help with?
Andy
