[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570849#action_12570849
]
Mark Harwood commented on LUCENE-794:
-------------------------------------
Actually is it worth trying to resolve this ConstantScoreRangeQuery issue?
1) A large range can produce a lot of terms - extracting these would bloat
memory and slow down highlighting.
2) The sorts of "quantity" fields that are subject to ranges (prices, dates,
lat-lon coordinates) don't typically need highlighting anyway because:
a) range criteria is normally mandatory (so ALL results are expected to
match the range and highlighting matches is unnecessary)
b) Quantities are normally held in dedicated fields with only one value.
Unlike free-text fields there's no need for the user's eye to scan large
amounts of information looking for the "hit" so, again highlighting/summarising
is generally less useful.
Given the unavoidable performance overhead this introduces and the sneaking
suspicion that it's not useful anyway is this worth supporting?
Would be keen to know what the scenario was that introduced this as a
requirement.
> Extend contrib Highlighter to properly support PhraseQuery, SpanQuery,
> ConstantScoreRangeQuery
> -----------------------------------------------------------------------------------------------
>
> Key: LUCENE-794
> URL: https://issues.apache.org/jira/browse/LUCENE-794
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Other
> Reporter: Mark Miller
> Priority: Minor
> Attachments: SpanHighlighter-01-26-2008.patch,
> SpanHighlighter-01-28-2008.patch, spanhighlighter.patch,
> spanhighlighter10.patch, spanhighlighter11.patch, spanhighlighter12.patch,
> spanhighlighter2.patch, spanhighlighter3.patch, spanhighlighter5.patch,
> spanhighlighter6.patch, spanhighlighter7.patch, spanhighlighter8.patch,
> spanhighlighter9.patch, spanhighlighter_24_January_2008.patch,
> spanhighlighter_patch_4.zip
>
>
> This patch adds a new Scorer class (SpanQueryScorer) to the Highlighter
> package that scores just like QueryScorer, but scores a 0 for Terms that did
> not cause the Query hit. This gives 'actual' hit highlighting for the range
> of SpanQuerys, PhraseQuery, and ConstantScoreRangeQuery. New Query types are
> easy to add. There is also a new Fragmenter that attempts to fragment without
> breaking up Spans.
> See http://issues.apache.org/jira/browse/LUCENE-403 for some background.
> There is a dependency on MemoryIndex.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
