Re: Issues with uniqueKey != id?

ger > IBM Deutschland Research & Development GmbH / Vorsitzende des > Aufsichtsrats: Martina Koederitz > Geschäftsführung: Dirk Wittkopp > Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, > HRB 243294 > > > > From: Susheel Kumar &

Re: Issues with uniqueKey != id?

I’m just setting that up now. I’m far from a Solr expert so I won’t swear we’re doing it right though Our issue is that we have documents, nested 3 deep. Products, Items, and SKUs. Each has an ID field that’s unique within the document type, but unfortunately we have products with the same

Re: Issues with uniqueKey != id?

ng else pop out I will let you know! Cheers - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/Issues-with-uniqueKey-id-tp4318662p4318944.html Sent from the So

Re: Issues with uniqueKey != id?

Amtsgericht Stuttgart, HRB 243294 From: Susheel Kumar <susheel2...@gmail.com> To: solr-user@lucene.apache.org Date: 05-02-17 03:21 AM Subject:Re: Issues with uniqueKey != id? Hello, So far in my experience haven't come across scenario where unique key/id is not requir

Re: Issues with uniqueKey != id?

Hello, So far in my experience haven't come across scenario where unique key/id is not required. Most of the times, I have put combination of few fields like aggregate or compound keys . (e.g. organization_id + employee_id etc.). The reason it makes

Issues with uniqueKey != id?

Howdy, In the Solr Wiki I stumbled upon a somewhat vague statement on the uniqueKey: > https://wiki.apache.org/solr/SchemaXml#The_Unique_Key_Field > It shouldn't matter whether you rename this to something else (and change the value), but occasionally it has in the past. We recommend that