Graph,
The complete javadoc for TDB2, API and internal is not there.
The API is:
http://jena.apache.org/documentation/javadoc/tdb2/org/apache/jena/tdb2/package-summary.html
(next release - that will be the javadoc c.f. TDB1)
Andy
On 06/08/18 04:59, graham wrote:
Hi
I click on the
It tells us that the problem seems more likely to be with TDB than with
Fuseki, which is a step towards isolating it.
Adam
On Mon, Aug 6, 2018, 5:55 AM Mikael Pesonen
wrote:
>
> With in-memory db everything works. Ran ~5 operations x10 (10
> scripts in parallel) and no problems. Mem usage
With in-memory db everything works. Ran ~5 operations x10 (10
scripts in parallel) and no problems. Mem usage was 3g-5,5g (java
xmx4000) and vm 10g.
So what does this tell? System is upcloud server so there shouldn't be
any issues with disk there...
Br,
On 3.8.2018 16:33, ajs6f
Sorry upcloud is Finnish cloud service provider.
On 6.8.2018 12:55, Mikael Pesonen wrote:
With in-memory db everything works. Ran ~5 operations x10 (10
scripts in parallel) and no problems. Mem usage was 3g-5,5g (java
xmx4000) and vm 10g.
So what does this tell? System is upcloud
Hi Rob!
Still about this problem of indexing, do you have some suggestion?
Em qui, 19 de jul de 2018 às 13:59, Alysson Gomes
escreveu:
> I did, but as you told the sparql launched an exception:
> org.apache.jena.sparql.ARQException: Found two matches: var ?root ->
>
graham,
Events and transaction isolation doesn't mix. Why being added, any
triples aren't visible outside the transaction; transactions can abort
resulting in no changes. So a kind of "within transaction" event might
make some sense (abort aside) but as a general concept it's a bit messy.
