I'd recommend you ignore search speed for the time being. First, your index isn't that large from what you've described. I see clients witn 40-50M documents on a single machine (admittedly with some iron under the hood)...
Instead, I'd concentrate on designing the best user experience I could, and worry about search speed only when your testing shows you need to. The real question isn't "will X or Y be faster" IMO, it's "Will what I want be fast enough". Using distinct fields and edismax is where I'd start. Best Erick On Thu, Aug 9, 2012 at 2:04 AM, santamaria2 <aravinda....@contify.com> wrote: > *civilized bump* > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Designing-an-index-with-multiple-entity-types-sharing-field-names-across-entity-types-tp3999727p4000051.html > Sent from the Solr - User mailing list archive at Nabble.com.
