Hi Enrico! > Is broken if you use it in plocal within a transcation using Java. >
Yes, exactly. Is this not a common usage scenario for OrientDB? I'm trying to understand it now... I'm evaluating Orient to replace current platform. Embedded Java DB with ACID and good search (integrated Lucene, cool), claimed to be production-ready. Good, I wrote several simple tests - just CRUD with Lucene indexes, nothing much. In transaction, of course - IMHO it is strange to use non-transactional DB with enterprise data... It fails in 2.0, it still fails in 2.1, so the result is - sorry, we cant use it May be Im wrong, and the main usage scenario is through rest api - OK, just write this in the description. May be Lucene integration is experimental and not to be used in production - OK, just write this. But IMHO you should have tests like these working in release, if you're going to be enterprise production ready - DB have to be reliant... For me it is far more important than adding more features - you already have a lot to be competing (yes, really) Thanks, > 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] <javascript:>>: > >> 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] <javascript:>. >> 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.
