Re: [orientdb] Multiple vertex objects referring to the same database record are not in sync

Indeed! All tests pass! Thank you! On Tuesday, October 28, 2014 9:52:22 AM UTC+1, Andrey Lomakin wrote: > > Fixed. > > On Fri, Oct 24, 2014 at 12:21 PM, Emanuele Milani > wrote: > >> Thank you very much! >> >> On Friday, October 24, 2014 9:49:11 AM UTC+2, And

Re: [orientdb] Multiple vertex objects referring to the same database record are not in sync

o Vertex objects refer to the same >> record? >> >> >> >> Thanks for clarifying this. >> >> >> >> Rani >> >> On Tuesday, October 21, 2014 1:03:08 PM UTC+2, Andrey Lomakin wrote: >>> >>> Hi >>> I got reaso

Re: [orientdb] Multiple vertex objects referring to the same database record are not in sync

[clean] [-U] test -Dtest=OrientTests* Thank you in advance! On Wednesday, October 22, 2014 11:48:40 AM UTC+2, Emanuele Milani wrote: > > Hi Andrey, > > I tried the same code with 2.0-SNAPSHOT (build 363), but unfortunetely the > problem is still there. Could you also replicate it? &g

Re: [orientdb] Multiple vertex objects referring to the same database record are not in sync

Hi Andrey, I tried the same code with 2.0-SNAPSHOT (build 363), but unfortunetely the problem is still there. Could you also replicate it? I also tried to check if my local cache is enabled, but I only found in the docs that it should be enabled by default. I am now adding a small maven project

Re: [orientdb] Multiple vertex objects referring to the same database record are not in sync

Hi Andrey, I tried the same code with 2.0-SNAPSHOT (build 363), but unfortunetely the problem is still there. Could you also replicate it? I am now adding a small maven project on github, which just contains 3 junit tests replicating the issue, and I will post the link as soon as I push it. As

Re: [orientdb] Multiple vertex objects referring to the same database record are not in sync

; > On Tue, Oct 21, 2014 at 1:59 PM, Andrey Lomakin > wrote: > >> Hi, >> Do you have local cache enabled ? >> It explicitly created to avoid such problems. >> >> On Tue, Oct 21, 2014 at 12:48 PM, Emanuele Milani > > wrote: >> >>> Hi

[orientdb] Multiple vertex objects referring to the same database record are not in sync

Hi all! I am in the process of debugging an application based on OrientDB (2.0M2). The problem I am facing are some OConcurrentModificationException. The issue appears with both the "memory" and the "plocal" storage engines (I did not try "remote"). It looks they are caused by the fact that mul

Re: [orientdb] Indexes are not updated until explicit commit in remote databases

2F%2Fgithub.com%2Forientechnologies%2Forientdb%2Fissues%2F1894&sa=D&sntz=1&usg=AFQjCNFOswse4xl3Bc3qu068Y3Q-XXGOfw> > > > On Fri, Mar 7, 2014 at 4:59 PM, Emanuele Milani > > > wrote: > >> Dear all, >> >> This same message is posted on both the

[orientdb] Indexes are not updated until explicit commit in remote databases

Dear all, This same message is posted on both the OrientDB and Gremlin-users groups, as I do not know whether this issue is related to Blueprints or OrientDB. For quite some time I have been using KeyIndexes (as in KeyIndexableGraph) with an embedded (database url starting with (p)local:) Orient

Re: [orientdb] batched transactions and not-yet-committed records

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, 20

[orientdb] batched transactions and not-yet-committed records

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 h