“bang for the
buck” for Jena users. One to which I keep coming back is the idea of
a dataset with per-graph transaction locking.
That might combine well with using the Graph Store Protocol for graph
management where default union graph is common.
Another locking strategy is "graph node
users. One to which I keep coming back is the idea of a dataset with
>> per-graph transaction locking.
>
> That might combine well with using the Graph Store Protocol for graph
> management where default union graph is common.
> Another locking strategy is "graph node" i.
to which I keep coming
back is the idea of a dataset with per-graph transaction locking. In other
words, a dataset wherein each named graph has a SW lock and the dataset as a
whole can support MRMW, as long as every writer is working in a different
graph. Some examples of where this could be helpful
On 09/12/15 13:22, A. Soroka wrote:
(after finishing what’s needed to RC-release the MR+SW in-memory dataset)
The build is done - the VOTE is open now. if the VOTE passes, that's it!
JIRA and maven are already bumped 3.1.0 next with versions now building
as 3.1.0-SNAPSHOT.
Andy
