: Say I have a product called "SUPERBOT" and I want the text "I love SUPERBOT"
: to match the product SUPERBOT pretty high.
The issue you're having is that by default, a document won't match a
dismax query unless all of the words in the query string match on at least
one of the "qf" fields ...
I have a dismax handler to match product names found in free text
that looks like:
explicit
0.01
name^5 nec_name^3 ne_name
*
100
*:*
name is type string, nec_name and ne_name are special types that do
domain-specif
As it happens, I put together an app that indexes books and
wrestled with this issue. NOTE: this was NOT solr, just straight
Lucene but I think my experience may apply. Also, I haven't
followed this entire thread, so I may be irrelevant...
First, the question of spanning across pages certainly was
On 10/19/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> (it doesn't matter that parseSort
> returns null when the sort string is just "score" ... SolrIndexSearcher
> recognizes a null Sort as being the default sort by score)
Yep... FYI, I did this early on specifically because "no sort" and
"sco
Hello,
I'm just thinking about a solution for a type ahead functionality
that shall suggest terms that the user can search for, and that
displays how many docs are "behind" that search (like google suggest).
When I use facet.prefix and facet.field=text, where text is my catchall
field (and defaul
