[LUCENE-5503] Trivial fixes to WeightedSpanTermExtractor

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.7
• Fix Version/s: 5.4
• Component/s: modules/highlighter
• Lucene Fields: New, Patch Available
• Assignee: David Smiley
• Reporter: Tim Allison
• Created: 07/Mar/14 20:30
• Updated: 28/Aug/22 14:02
• Resolved: 13/Sep/15 04:09

Description

The conversion of PhraseQuery to SpanNearQuery miscalculates the slop if there are stop words in some cases. The issue only really appears if there is more than one intervening run of stop words: ab the cd the the ef.

I also noticed that the inOrder determination is based on the newly calculated slop, and it should probably be based on the original phraseQuery.getSlop()

patch and unit tests on way