I think I just need to set the log level to "INFO" to surpass this particular exception, but for some reason, in my case, it created some wired empty vertices with no class or no name. :( :(
On Monday, August 21, 2017 at 4:26:02 PM UTC-7, Rajendra Prasad Gujja wrote: > > Hi Gregor, > > I still see this problem, is there any fix for this? > > Thanks, > RP. > > On Monday, February 16, 2015 at 8:30:11 AM UTC-8, Gregor Frey wrote: >> >> Hi, >> just for a test I patched the class OVertexTransformer to ignore >> ORecordDuplicatedExceptions. But then I found that when the >> OAbstractTransformer was about to log the missing of the document, I got >> the same exception again. The reason is that the toString() method of the >> OVertex implicitly calls a save, which then throws the exception. See the >> stack trace below. But, perhaps even more importantly, I was wondering >> whether I you wouldn't expect the toString() method to have no >> side-effects? This could also become a performance issue in the end. I'm >> not in the details, of course. But from a high-level point of view, I think >> it would be better to not even try to do any data modifications within a >> toString() method. >> Ciao >> Gregor >> >> >> >> > -- --- 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.
