When you index into Solr, you are overlapping the definitions into one schema. Therefore, you will need a unified uniqueKey.
There is a couple of approaches: 1) Maybe you don't actually store the data as three types of entities. Think about what you will want to find and structure the data to match. Doing JOINS in Solr is a bad idea, even if sometimes possible 2) Make a compositeKey as unique key by adding type prefix to your key ids when exporting to SQL (select concat('r',id), .....) 3) Make a compositeKey as unique key by using UpdateRequestProcessors to manipulate the value of the uniqueKey field. You'd need three different update chains to apply different prefixes, but you can pass the chain name as a request parameter. You can find the full list of the URPs at: http://www.solr-start.com/info/update-request-processors/ Regards, Alex. ---- Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start.com/ On 17 November 2015 at 08:14, Mugeesh Husain <muge...@gmail.com> wrote: > Hi! > > I have a 3 csv table, > 1.)retuarant > 2.)User > 3.)Review > > every csv have a unique key, then how i can configure multiple unique key in > solr > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Multiple-unique-key-in-Schema-tp4240550.html > Sent from the Solr - User mailing list archive at Nabble.com.