Hello Andy,
sorry for my very, very late answer. We rolled out many new features on
our platform in the last weeks, so I was too busy to integrate our TDB
0.8.10 changes to TDB 0.9. Yesterday I started again.
Our unit tests print out a ConcurrentModificationException if we iterate
over the mod
On 13/11/12 12:26, "Dr. André Lanka" wrote:
Hi Andy,
On 12.11.2012 18:21, Andy Seaborne wrote:
Is each store using named graphs? Or is one store, one graph?
One store is one default graph without any special named graphs along.
The reason for having multiple stores is that we need write acce
Hi Andy,
On 12.11.2012 18:21, Andy Seaborne wrote:
Is each store using named graphs? Or is one store, one graph?
One store is one default graph without any special named graphs along.
The reason for having multiple stores is that we need write access to
each graph in parallel. Serialising t
On 12/11/12 13:04, "Dr. André Lanka" wrote:
Hi Andy,
thanks for your answer. I really missed 0.9.4. You are right, the issues
vanished with the new version. Thanks for the hint.
By the way: We're just patching 0.9.4 to provide a global cache (for
both reading and writing) for both Nodes and Blo
Hi Andy,
thanks for your answer. I really missed 0.9.4. You are right, the issues
vanished with the new version. Thanks for the hint.
By the way: We're just patching 0.9.4 to provide a global cache (for
both reading and writing) for both Nodes and Blocks in direct file mode.
This means that
Have you tried version 0.9.4?
It has fixes that may apply to your situation.
Andy
On 06/11/12 08:33, "Dr. André Lanka" wrote:
Hello (once more),
the problem could be fixed by doing the following:
BlockMgrJournal: Add "blockMgr.sync();" to sync()
NodeTableTrans: Add "base.sync();" to
Hello (once more),
the problem could be fixed by doing the following:
BlockMgrJournal: Add "blockMgr.sync();" to sync()
NodeTableTrans: Add "base.sync();" to sync()
Yet, I don't know what side effects this would have. Could some of the
tdb specialists judge these changes?
Best wishes
André
Hello TDB developers
thanks for you great work :)
Unfortunately, I encountered some problems while testing TDB 0.9.3. It
turned out that a dataset.commit() doesn't force NodeTableNative to
write the whole data to disk or that NodeTableNative.syncNeeded wasn't
set properly earlier.
By this,
