I implemented both solutions Hoss suggested and was able to achieve the
desired results. I would like to go with
defType=dismax qf=myname pf=myname_str^100 q=Frank
but that doesn't seem to work if I have a query like myname:Frank
otherfield:something. So I think I will go with
That's a clever idea. I'll put something together and see how it turns out.
Thanks for the tip.
On Wed, Jul 27, 2011 at 10:55 PM, Chris Hostetter
hossman_luc...@fucit.orgwrote:
: With your solution, RECORD 1 does appear at the top but I think thats
just
: blind luck more than anything else
Keep in mind that if you use a field type that includes spaces (eg
StrField, or KeywordTokenizer), then if you're using dismax or lucene
query parsers, the only way to find matches in this field on queries
that include spaces will be to do explicit phrase searches with double
quotes.
These
Thanks Emmanuel for that explanation. I implemented your solution but I'm
not quite there yet. Suppose I also have a record:
RECORD 3
arr name=myname
strFred G. Anderson/str
strFred Anderson/str
/arr
With your solution, RECORD 1 does appear at the top but I think thats just
blind luck more
: With your solution, RECORD 1 does appear at the top but I think thats just
: blind luck more than anything else because RECORD 3 shows as having the same
: score. So what more can I do to push RECORD 1 up to the top. Ideally, I'd
: like all three records returned with RECORD 1 being the first
Hi all,
I am a little confused as to why the scoring is working the way it is:
I have a field defined as:
field name=myname type=text indexed=true stored=true
required=false multivalued=true /
And I have several documents where that value is:
RECORD 1
arr name=myname
strFred/str
strFred
That is caused by the size of the documents. The principle is pretty
intuitive if one of your documents is the entire three volumes of The Lord
of the Rings, and you search for tree I know that The Lord of the Rings
will be in the results, and I haven't memorized the entire text of that book
:p
It
