The easiest way to think about it is that the “mm” parameter is a sliding scale
between
pure OR and pure AND, i.e. any clause that matches returns the doc (0) and all
clauses
must be matched (100) for the doc to be returned…
But no, I don’t know of any other explanation pages for that parameter.
Following Erik idea, I started to look in different fields or queries than
the title field itself, and I started using the normal requesthandler
(/select) and adding parameters to see if any of the parameters in my query
make this problem.
And I discovered that in my customize RequestHandler I'm us
First, if you _changed_ the analysis chain without re-indexing all documents,
that could account for it.
Second, the analysis page is a little tricky. It _assumes_ that the words you
put in the boxes have been parsed into the field you select. So let’s say you
have this field “title” that has s
Thank you for the answer and heading me to this solution. But I've already
used this filter for index analysis and I'm not getting any result. So I
don't understand why I'm not getting the result.
If I use the Analysis tool, I'm gettin
So, maybe the problem is other? But I don't see what can be the
On 3/1/2019 4:38 AM, Marisol Redondo wrote:
When using the PorterStemFilter, I saw that the work "employing" is change
to "emploi" and my document is not found in the query to solr because of
that.
This also happens with other words that finish in -ying as annoying or
deploying.
It there any pa
Hi.
When using the PorterStemFilter, I saw that the work "employing" is change
to "emploi" and my document is not found in the query to solr because of
that.
This also happens with other words that finish in -ying as annoying or
deploying.
It there any path for this filter or should I create a n
