Ok, so we may want to add a little xdmp:sleep() after the document insert
instruction I guess. Thanks for your help.
cheers,
Jakob.
On Tue, May 6, 2014 at 5:53 PM, John Snelson wrote:
> Triple index updates are transactional, so you can see them as soon as
> the inserting transaction has comple
Triple index updates are transactional, so you can see them as soon as
the inserting transaction has completed. I suspect you're seeing a race
conditions with the inserting transaction.
John
On 06/05/14 16:22, Jakob Fix wrote:
> John,
>
> Maybe a misunderstanding in my message: We're inserting
John,
Maybe a misunderstanding in my message: We're inserting the XML document
which triggers the pre-commit trigger that generates the triple document in
a *separate transaction from the test itself*, in order to be able to query
it. For this to work, we're inserting the document via an HTTP POST
On 06/05/14 15:17, Jakob Fix wrote:
> we are doing xray unit testing for our application, and one of the
> issues we run into occasionally is that even though we know that triples
> have been created and stored as triple documents, they are not always
> (but sometimes) found when executing a sparql
Hello,
we are doing xray unit testing for our application, and one of the issues
we run into occasionally is that even though we know that triples have been
created and stored as triple documents, they are not always (but sometimes)
found when executing a sparql query in the same test. by the way,
