Thank you for your reply and sorry for not being too clear in the first 
place...

My goal is to control the number of database commits during a large data 
import via a configuration parameter (batch-size). Every time my code wants 
to commit, a counter is increased. When the counter reaches the batch-size, 
an actual commit is performed and the counter is reset.
Part of the import process it a "fetch or create" operation, which 
retrieves a node given a property/value pair if existing (a lookup), and 
creates it otherwise.
Everything works fine when I use an ambedded database (i.e. the database 
url starts with "plocal:"). However, if I use an external database server 
and the batch_size is large enough, some inserted nodes are not visible for 
the lookups, even if I am accessing the db with one single client. Any idea 
why?

I am currently trying to isolate the problem. Unfortunately it is taking 
more time than I thought.
 
Thanks again for your help!


On Monday, February 17, 2014 1:36:31 PM UTC+1, Andrey Lomakin wrote:
>
> Hi,
> Sorry I did not get, what is your problem, could you provide example ?
>
>
>
>
> On Fri, Feb 14, 2014 at 5:49 PM, Emanuele Milani 
> <[email protected]<javascript:>
> > wrote:
>
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> Best regards,
> Andrey Lomakin.
>
> Orient Technologies
> the Company behind OrientDB
>
>  

-- 

--- 
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.

Reply via email to