On 16/11/17 18:00, Jean-Marc Vanel wrote:
/With TDB2, is it bad to share a Dataset across threads and transactions ?
What are the don't 's regarding TDB2 API use ?/
Got my (email) threads mixed up ... on another thread today:
"""
TDB2 goals are to address the scale limitations on transactions, the
write-back queue overload problems, a better architecture e.g. fully
integrate in jena-text transactions, and no quirks about models across
transactions.
"""
http://jena.apache.org/documentation/tdb2/
It is not bad.
It *should* work - it's supposed to.
As does (when some recent fixes go in): Graph.TransactionHandler.begin()
including automatic promotion from R to W as required by that API.
It's in the test suite for "across transaction, same thread" and I can't
remember for multithread. The core engine for TDB2 was written a couple
of years ago; I forget details.
Transactions at the API level are per thread, internally they are not.
Andy
