: However, is there an actual fix in the 3.1 eDisMax parser which solves
: the problem for real? Cannot find a JIRA issue for it.
edismax uses the same query structure as dismax, which means it's not
possible to "fix" anything here ... it's how the query parsers work.
each "word" from the quer
A thread with this same subject from 2008/2009 is here:
http://search-lucene.com/m/jkBgXnSsla
We're seeing customers being bitten by this "bug" now and then, and normally my
workaround is to simply not use stopwords at all.
However, is there an actual fix in the 3.1 eDisMax parser which solves t
: Hmm, that makes sense to me - however I still think that even if we have mm
: set to "2" and we have "the 7449078" it should still match 7449078 in a
: productId field (it does not:
: http://zeta.zappos.com/search?department=&term=the+7449078). This seems like
: it works against the way one woul
Hmm, that makes sense to me - however I still think that even if we
have mm set to "2" and we have "the 7449078" it should still match
7449078 in a productId field (it does not: http://zeta.zappos.com/search?department=&term=the+7449078)
. This seems like it works against the way one would rea
: Would this mean that, for example, if we wanted to search productId (long)
: we'd need to make a field type that had stopwords in it rather than simply
: using (long)?
not really ... that's kind of a special usecase. if someone searches for
a productId that's usually *all* they search for (1
Would this mean that, for example, if we wanted to search productId
(long) we'd need to make a field type that had stopwords in it rather
than simply using (long)?
Thanks for your time!
Matthew Runo
Software Engineer, Zappos.com
mr...@zappos.com - 702-943-7833
On Dec 12, 2008, at 11:56 PM,
: I have discovered some weirdness with our Minimum Match functionality.
: Essentially it comes up with absolutely no results on certain queries.
: Basically, searches with 2 words and 1 being ³the² don¹t have a return
: result. From what we can gather the minimum match criteria is making it
: su
I have discovered some weirdness with our Minimum Match functionality.
Essentially it comes up with absolutely no results on certain queries.
Basically, searches with 2 words and 1 being ³the² don¹t have a return
result. From what we can gather the minimum match criteria is making it
such that if
