I believe I have applied the patch correctly. However, I cannot seem to
figure out where the similarity class I create should reside. Any tips on
that?
Thanks,
Brian Lamb
On Tue, May 17, 2011 at 4:00 PM, Brian Lamb
wrote:
> Thank you Robert for pointing this out. This is not being used for
> au
Thank you Robert for pointing this out. This is not being used for
autocomplete. I already have another core set up for that :-)
The idea is like I outlined above. I just want a multivalued field that
treats every term in the field the same so that the only way documents
separate themselves is by
Well, if you're experimental you can try trunk as Robert points out it has
been fixed there. If not, i guess you're stuck with creating another core.
If this fieldType specifically used for auto-completion? If so, another core,
preferably on another machine, is in my opinion the way to go. Auto-
On Tue, May 17, 2011 at 3:34 PM, Markus Jelsma
wrote:
> If you still want IDF for other fields then i
> think you have a problem because Solr doesn't yet support per-field
> similarity.
>
it does in trunk: https://issues.apache.org/jira/browse/SOLR-2338
Hi Markus,
I was just looking at overriding DefaultSimilarity so your email was well
timed. The problem I have with it is as you mentioned, it does not seem
possible to do it on a field by field basis. Has anyone had any luck with
doing some of the similarity functions on a field by field basis? I
Hi,
Although you can configure per field TF (by omitTermFreqAndPositions) you can't
do this for IDF. If you index is only used for this specific purpose (seems
like an auto-complete index) then you can override DefaultSimilarity and
return a static value for IDF. If you still want IDF for other
