Hi all! In my application I am trying to "batch" transactions, so that actual commit() are called every k (batch size) "virtual" commit(). The idea is to trade-off between high granularity commits and better perfromance.
The problem is that the code performs a lookup for a node which may not have been committed yet. The lookup seems to work using db urls with "local" prefix. With "remote", however, if the batch size is bigger than a certain threshold, the lookup fails, even if I have one single client and one single server. Is there some concurrent behavior that I am missing? Software used: OrientDB 1.6.4, Tinkerpop 2.5.0-SNAPSHOT Thanks for your help! -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
