[
https://issues.apache.org/jira/browse/LUCENE-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Stein updated LUCENE-7038:
-------------------------------
Description:
This is a regression since Lucene 4.10 regarding The QueryScorer class in the
Highlighter module.
In 4.10, the {{QueryScorer.init}} method returns a working tokenStream even if
the maxCharsToAnalyze variable is set to zero. In both versions, zero is the
default value and in 4.10 it indicated that the entire stream should be
returned, not an empty stream.
The problem is with the {{WeightedSpanTermExtractor}} always wrapping the
tokenStream in a {{OffsetLimitTokenFilter}} filter, even when the passed down
maxDocCharsToAnalyze variable is zero.
was:
This is a regression since Lucene 4.10 regarding The QueryScorer class in the
Highlighter module.
In 4.10, the `QueryScorer.init` method returns a working tokenStream even if
the maxCharsToAnalyze variable is set to zero. In both versions, zero is the
default value and in 4.10 it indicated that the entire stream should be
returned, not an empty stream.
The problem is with the `WeightedSpanTermExtractor` always wrapping the
tokenStream in a `OffsetLimitTokenFilter` filter, even when the passed down
maxDocCharsToAnalyze variable is zero.
> QueryScorer.init returns empty TokenStream if setMaxDocCharsToAnalyze is not
> previously called
> ----------------------------------------------------------------------------------------------
>
> Key: LUCENE-7038
> URL: https://issues.apache.org/jira/browse/LUCENE-7038
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/highlighter
> Affects Versions: 5.4
> Reporter: Jeff Stein
> Priority: Minor
>
> This is a regression since Lucene 4.10 regarding The QueryScorer class in the
> Highlighter module.
> In 4.10, the {{QueryScorer.init}} method returns a working tokenStream even
> if the maxCharsToAnalyze variable is set to zero. In both versions, zero is
> the default value and in 4.10 it indicated that the entire stream should be
> returned, not an empty stream.
> The problem is with the {{WeightedSpanTermExtractor}} always wrapping the
> tokenStream in a {{OffsetLimitTokenFilter}} filter, even when the passed down
> maxDocCharsToAnalyze variable is zero.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
