Hi Valeri Actually is not broken. Is broken if you use it in plocal within a transcation using Java. I know that is important and has to be fixed but is not an easy task and it is not a simple fix. However I'm working on this
2015-09-14 10:27 GMT+02:00 <[email protected]>: > OK, it isnt fixed in 2.1.2 > > Guys, may be I dont understand something? Lucene integration is broken, it > was declared part of OrientDB. You told me that "we need to improve Lucene > integration" - IMHO first it should be fixed. Issue was posted in June for > 2.0, now it is September, 2.1.2... > > IMHO it is meaningless to add functionality to the product, if it is just > broken > > > > On Monday, August 10, 2015 at 1:18:29 PM UTC+3, Enrico Risa wrote: >> >> This is not OrientDB problem, but the integration with lucene >> >> We have an open issue to improve TX management see here >> >> https://github.com/orientechnologies/orientdb-lucene/issues/46 >> >> 2015-08-10 12:05 GMT+02:00 <[email protected]>: >> >>> Hi Enrico, thanks for fast answer >>> >>> Yes, I wrote in the issue, that problem is changes + query inside >>> transaction. Is it normal for OrientDB? >>> >>> In other databases, queries are to be run in transactional context, and >>> results are in sync with local changes. If it is forbidden in OrientDB - >>> well, write it as restriction >>> >>> >>> >>> On Monday, August 10, 2015 at 12:44:57 PM UTC+3, Enrico Risa wrote: >>>> >>>> Hi >>>> >>>> i've checked it see here >>>> >>>> https://github.com/orientechnologies/orientdb/issues/4257 >>>> >>>> 2015-08-10 11:26 GMT+02:00 <[email protected]>: >>>> >>>>> OK, it exists in 2.1.0 GA. I posted simple code to reproduce, have you >>>>> just fast-checked it? >>>>> >>>>> I tried to evaluate OrientDB (2.0 & 2.1) several times, and always was >>>>> stopped by blockers. It is claimed to be rock-solid, may be I do something >>>>> wrong? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Thursday, July 30, 2015 at 10:24:06 AM UTC+3, [email protected] >>>>> wrote: >>>>>> >>>>>> Hi! >>>>>> >>>>>> This was found 2 months ago in 2.0.10 , I can reproduce it in 2.1-rc6 >>>>>> https://github.com/orientechnologies/orientdb/issues/4257 >>>>>> >>>>>> >>>>>> IMHO it is blocker, at least I cant use lucene indexes (yes, we need >>>>>> mixed transactions with searches and updates in one transaction). Is this >>>>>> issue planned to be fixed in 2.1 GA? >>>>>> >>>>>> Thanks >>>>>> >>>>>> -- >>>>> >>>>> --- >>>>> 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/d/optout. >>>>> >>>> >>>> -- >>> >>> --- >>> 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/d/optout. >>> >> >> -- > > --- > 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/d/optout. > -- --- 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/d/optout.
