Hi Curtis, It's not related to the property name that are the same if the class/table is different. Seems the value "11082323" has been already indexed by reading the record #12:102. Can you check that records #12:102 and #12:109 have the same person_id?
Lvc@ ᐧ On 21 August 2014 13:17, 'Curtis Mosters' via OrientDB < [email protected]> wrote: > Let's say I have two tables in MySQL. > > both have a column name *person_id*. Now I imported everything to > OrientDB. So I have let's say the Class "*Person*" and "*Appln*". > > Both have of course "*person_id*" as property. Now I created an index on > Person.person_id. Works perfect. But when I now try to create an index on > Appln.person_id I get this one here: > > com.orientechnologies.orient.core.index.OIndexException: Error on > rebuilding the index for clusters: [appln] --> com.orientechnologies. > orient.core.storage.ORecordDuplicatedException: Cannot index record #12:109: > found duplicated key '11082323' in index 'Appln.person_id' previously > assigned to the record #12:102 RID=#12:102 > > Well I know why this error comes. Because it's the same property name. But > what should I do now? Renaming cannot be a good way to solve ths issue I > think. > Any other idea? > > -- > > --- > 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.
