[SERVER-12195] Text matcher uses incorrect language for negation match Created: 23/Dec/13 Updated: 11/Jul/16 Resolved: 13/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Text Search |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
The text negation matcher parses the document using the search language. It should instead be parsing the document with the document language.
|
| Comments |
| Comment by Githook User [ 13/Feb/14 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: This fixes the issue that the text matcher was incorrectly parsing |
| Comment by Eliot Horowitz (Inactive) [ 23/Dec/13 ] |
|
Documents are always parsed in doc language. |