apache / apache/lucene

In SpanNearQuery, add support for inOrder semantics equivalent to that of (Multi)PhraseQuery [LUCENE-8544]

Open
#9,590 3 comments 0 reactions 0 assignees View on GitHub
legacy-jira-priority:Minor module:core/search type:enhancement
Dominant language
Java
Stars
3.6k
Forks
1.4k
Avg merge
2d 11h
Merged PRs (30d)
88

Description

As discussed in #9577, the semantics of phrase search differs among `(Multi)PhraseQuery`, `SpanNearQuery (inOrder=true)`, and `SpanNearQuery (inOrder=false)`:
- `(Multi)PhraseQuery`: incorporates the concept of order, and allows negative offsets in calculating slop/edit distance
- `SpanNearQuery (inOrder=true)`: incorporates the concept of order, and does _not_ allow negative offsets in calculating slop/edit distance
- `SpanNearQuery (inOrder=false)`: does not incorporate the concept of order at all

This issue concerns the possibility of adjusting `SpanNearQuery` to be configurable to support semantics equivalent to that of `(Multi)PhraseQuery`.

---
Migrated from [LUCENE-8544](https://issues.apache.org/jira/browse/LUCENE-8544) by Michael Gibney (@magibney), updated Nov 05 2018

Contributor guide

Open the contributing guide

Research direction

Start by reading the semantics described here and the linked discussion in #9577, then review the migrated LUCENE-8544 issue. Determine the agreed configurable behavior for SpanNearQuery and how it should match (Multi)PhraseQuery; done means the scope and equivalent in-order semantics are established and validated.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.