lution that you mentioned in your reply. you can always have string field
> and in your pf parameter you can boost that field to get the exact match
> results on top.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.na
results on top.
Thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/string-field-does-not-yield-exact-match-result-using-qf-parameter-tp4060096p4060492.html
Sent from the Solr - User mailing list archive at Nabble.com.
Why I am seeing this behavior.
>
> is there anyway to say qf=f1 on the interface and get only exact results if
> present (in this case though f1 is string but the q parameter has spaces. do
> I need to use pf field
> I am using dismax query parser.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/string-field-does-not-yield-exact-match-result-using-qf-parameter-tp4060096.html
> Sent from the Solr - User mailing list archive at Nabble.com.
the interface and get only exact results if
present (in this case though f1 is string but the q parameter has spaces. do
I need to use pf field
I am using dismax query parser.
Thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/string-field-does-not-yield-exact-match-result-u
