Does that flag also work on Edges so that edges don't get duplaicated? Also, how does it know what the definition of "duplicate" is? Does it look for the existence of a UNIQUE INDEX and use that? If so, then I must necessarily have a UNIQUE INDEX on the vertex ... or is that why you provide the ability to define an index in the ETL control document?
Thanks! On Wednesday, March 11, 2015 at 4:20:59 AM UTC-4, Lvc@ wrote: > > Hi Patrick, > See skipDuplicates option in > http://www.orientechnologies.com/docs/last/orientdb-etl.wiki/Transformer.html#vertex > > Lvc@ > > > On 10 March 2015 at 23:02, Patrick Hoeffel <[email protected] > <javascript:>> wrote: > >> I'm doing batch loading of data into my OrientDB database. On initial >> load the data is all new, so no issues, but if I need to update data later, >> in bulk, is there a way to use the OETL tool to specify "IF EXISTS (PK) >> UPDATE, ELSE INSERT;" >> I've looked through the documentation, but can't seem to find an answer. >> >> Thanks, >> >> Patrick >> >> -- >> >> --- >> 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.
