alessandrobenedetti opened a new pull request #158:
URL: https://github.com/apache/solr/pull/158


   https://issues.apache.org/jira/browse/SOLR-15449
   
   # Description
   
   When a field text analysis is incompatible with the query text, mm is not 
fully respected:
   ```
   sow = false
   mm=100%
   qf = text numeric_i
   q = terminator 100
   defType = edismax
   "parsedquery_toString":
   "+(((text:terminator text:100)~2) | 
   (numeric_i:100)~1))"
   A document just containing '100' in the field numeric_i is returned as a 
good search result but it actually doesn't respect the mm=100%
   ```
   
   # Solution
   
   Instead of just ignoring un-parsable clauses, a noMatch query is added
   
   # Tests
   
   tests have been added to: org.apache.solr.search.TestExtendedDismaxParser
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [X] I have reviewed the guidelines for [How to 
Contribute](https://wiki.apache.org/solr/HowToContribute) and my code conforms 
to the standards described there to the best of my ability.
   - [X] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [X] I have given Solr maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended)
   - [X] I have developed this patch against the `main` branch.
   - [X] I have run `./gradlew check`.
   - [X] I have added tests for my changes.
   - [ ] I have added documentation for the [Reference 
Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to