Bill,
I was using it as a simple default search field. I realise now that's not
a good reason to use copyField. As I see it now, it should be used if you
want to search in a way that is different: use different analyzers, etc; not
for just searching on multiple fields in a single query.
Thank
It depends.
copyField may be good if you want to copy into a Soundex field, and then
boost the sounded field lower than the tokenized field.
What are you trying to do ?
On 8/22/11 11:14 AM, "Tom" wrote:
>Is it a good rule of thumb, that when dealing with large indexes copyField
>should not be
Thanks Erick
--
View this message in context:
http://lucene.472066.n3.nabble.com/copyField-for-big-indexes-tp3275712p3275816.html
Sent from the Solr - User mailing list archive at Nabble.com.
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
