copyField should only be used if there's a good reason, that is you need to tokenize/analyze stuff differently, for instance faceting.
It's not so much a matter of the index size, as whether the copyFields are necessary to get your needed functionality. You're right that you can construct queries across several fields as your example. Another strategy would be to just use (e)dismax. Best Erick On Mon, Aug 22, 2011 at 1:14 PM, Tom <springmeth...@gmail.com> wrote: > Is it a good rule of thumb, that when dealing with large indexes copyField > should not be used. It seems to duplicate the indexing of data. > > You don't need copyField to be able to search on multiple fields. Example, > if I have two fields: title and post and I want to search on both, I could > just query > title:<word> OR post:<word> > > So it seems to me if you have lot's of data and a large indexes, copyField > should be avoided. > > Any thoughts? > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/copyField-for-big-indexes-tp3275712p3275712.html > Sent from the Solr - User mailing list archive at Nabble.com. >
