"The main motivation is to support a geo-specific relevancy model which can easily be customized without stepping into each other"
Is your relevancy tuning massively index time based ? i.e. will create massively different index content based on the geo location ? If it is just query time based or lightly index based ( few fields of difference across region), you don't need different collections at all to have a customized relevancy model per use case. In Solr you can define different request handlers with different query parsers and search components specifications. If you go in deep with relevancy tuning and for example you experiment Learning To Rank, it supports passing the model name at query time, which means you can use a different relevancy mode just passing it as a request parameter. Regards ----- --------------- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
