[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760083#action_12760083
]
Mark Miller edited comment on SOLR-1221 at 9/27/09 12:36 PM:
-------------------------------------------------------------
Sorry - should have been more clear.
The bug is hidden on trunk at the moment - Koji pointed out that I missed a
spot, and on trunk right now, queries are being rewritten by default when they
shouldnt be.
Now that you mention it though, the issue is not just with NumericRange (I just
assumed that was being gen'd cause I saw the problem with it), but its also
going to be with the
deprecated RangeQuery it looks. *edit* actually - since RangeQuery no longer
extends MultiTermQuery, it won't cause the error - it just won't highlight.
*edit*
which really argues for a jar update - I can fix all causes with one simple fix
- checking if getTerm returns null.
was (Author: [email protected]):
Sorry - should have been more clear.
The bug is hidden on trunk at the moment - Koji pointed out that I missed a
spot, and on trunk right now, queries are being rewritten by default when they
shouldnt be.
Now that you mention it though, the issue is not just with NumericRange (I just
assumed that was being gen'd cause I saw the problem with it), but its also
going to be with the
deprecated RangeQuery it looks.
*edit*
which really argues for a jar update - I can fix all causes with one simple fix
- checking if getTerm returns null.
> Change Solr Highlighting to use the SpanScorer with MultiTerm expansion by
> default
> ----------------------------------------------------------------------------------
>
> Key: SOLR-1221
> URL: https://issues.apache.org/jira/browse/SOLR-1221
> Project: Solr
> Issue Type: Improvement
> Components: highlighter
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 1.4
>
> Attachments: SOLR-1221.patch, SOLR-1221.patch, SOLR-1221.patch,
> SOLR-1221.patch
>
>
> To improve the out of the box experience of Solr 1.4, I really think we
> should make this change. You will still be able to turn both off.
> Comments?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
