Hi Eric, Thanks for your response. I was planning to do the same, to store the data in a single collection with site parameter differentiating duplicated content for different sites. But my use case is that in future the content would run into millions and potentially there could be large number of sites as well. Hence I am trying to arrive at a solution that can be best of both worlds. Is there any efficient way to store preventing duplication, merging the site specific and common content, and still be able to edit record for individual site without having to index the entire block.
Thanks, Sriram -- View this message in context: http://lucene.472066.n3.nabble.com/solr-index-design-for-this-use-case-tp4200000p4200065.html Sent from the Solr - User mailing list archive at Nabble.com.
