Disable cross-matches on multi-valued fields [LUCENE-3322]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
When searching against a multi-valued field it is often advantageous to disable cross-matches. For instance, if a book contains two authors: "john smith" and "brian jones", a search for "john jones" should not match.
Currently the best workaround is to search using a sloppy phrase query. The drawback is that phrases are incompatible with other features such as wildcards and ranges. Additionally, it is left up to the user to know to formulate the query differently if searching a multi-valued field.
---
Migrated from [LUCENE-3322](https://issues.apache.org/jira/browse/LUCENE-3322) by James Dyer (@jdyer1)
Attachments: [LUCENE-3322.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-3322/LUCENE-3322.patch)
Contributor guide
Research direction
Start by reviewing the attached LUCENE-3322.patch and the issue's multi-valued field example, then trace the query behavior involved in cross-matches. Done means searches such as “john jones” no longer match separate values while wildcards and ranges remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100