I'll take a stab. IMHO, it doesn't make much sense to propagae the boost, and here's why:
For the typical use case, copyField is used to add other "searchable" fields into the default "text" field for Standard queries. Say we are copying the ModelNumber field into the text field, and we have a boost of 5.0 for the ModelNumber field. Now, that means any document with a ModelNumber value would have the extra boost of 5.0 multiplied into the boost of the "text" field, for ALL terms in "text"; whereas documents with no ModelNumber would get no such benefit, completely skewing the results This would only make sense if boosts are per field instance and not per field, but we know that's not the case. Am I making sense? Yu-Shan On Tue, Feb 16, 2010 at 10:54 PM, Chris Hostetter <hossman_luc...@fucit.org>wrote: > > : > I belive Koji was mistaken. looking at DocumentBuilder.toDocument, the > : > boosts have been propogated to copyField destinations since that method > was > : > added in 2007 (initially it didn't deal with copyfields at all, but > once > : > that was fixed it copied the boosts as well.) > ... > : Hmm, I didn't know it. Thanks for correcting me. > : But is it (propagating boost) good idea? What is use case for? > > No clue, to either question ... i have no opinion on wether or not it > makes sense, i'm just telling you what i see in the code. > > > -Hoss > > -- “When nothing seems to help, I go look at a stonecutter hammering away at his rock perhaps a hundred times without as much as a crack showing in it. Yet at the hundred and first blow it will split in two, and I know it was not that blow that did it, but all that had gone before.” — Jacob Riis
