On Tue, 07 Oct 2008 09:27:30 -0700
Jon Drukman [EMAIL PROTECTED] wrote:
Yep, you can fake it by only using fieldsets (qf) that have a
consistent set of stopwords.
does that mean changing the query or changing the schema?
Jon,
- you change schema.xml to define which type each field is.
Norberto Meijome wrote:
On Tue, 07 Oct 2008 09:27:30 -0700
Jon Drukman [EMAIL PROTECTED] wrote:
Yep, you can fake it by only using fieldsets (qf) that have a
consistent set of stopwords.
does that mean changing the query or changing the schema?
Jon,
- you change schema.xml to define which
On 7-Oct-08, at 9:27 AM, Jon Drukman wrote:
Mike Klaas wrote:
On 6-Oct-08, at 11:20 AM, Jon Drukman wrote:
is there any way i could 'fake' it by adding a second field
without stopwords, or something like that?
Yep, you can fake it by only using fieldsets (qf) that have a
consistent set
Mike Klaas wrote:
On 6-Oct-08, at 11:20 AM, Jon Drukman wrote:
Chris Hostetter wrote:
It's not a bug in the implementation, it's a side effect of the basic
tenent of how dismax works since it inverts the input and creates a
DisjunctionMaxQuery for each word in the input, any word that is
Chris Hostetter wrote:
It's not a bug in the implementation, it's a side effect of the basic
tenent of how dismax works since it inverts the input and creates a
DisjunctionMaxQuery for each word in the input, any word that is valid
in at least one of the qf fields generates a should clause
On 6-Oct-08, at 11:20 AM, Jon Drukman wrote:
Chris Hostetter wrote:
It's not a bug in the implementation, it's a side effect of the
basic tenent of how dismax works since it inverts the input and
creates a DisjunctionMaxQuery for each word in the input, any
word that is valid in at least
i have a document with the following field
nameSaying goodbye to Norman/name
if i search for saying goodbye to norman with the standard query, it
works fine. if i specify dismax, however, it does not match. here's
the output of debugQuery, which I don't understand at all:
str
