[
https://issues.apache.org/jira/browse/LUCENE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742327#comment-14742327
]
ASF subversion and git services commented on LUCENE-5503:
---------------------------------------------------------
Commit 1702697 from [~dsmiley] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1702697 ]
LUCENE-5503: Highlighter WSTE didn't always convert a PhraseQuery to a
SpanQuery correctly.
> Trivial fixes to WeightedSpanTermExtractor
> ------------------------------------------
>
> Key: LUCENE-5503
> URL: https://issues.apache.org/jira/browse/LUCENE-5503
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/highlighter
> Affects Versions: 4.7
> Reporter: Tim Allison
> Assignee: David Smiley
> Priority: Minor
> Fix For: 5.4
>
> Attachments: LUCENE-5503.patch, LUCENE-5503.patch, LUCENE-5503v2.patch
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
