[
https://issues.apache.org/jira/browse/LUCENE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642617#action_12642617
]
Uwe Schindler commented on LUCENE-1424:
---------------------------------------
Just a suggestion:
How about *not* inventing new Class names. Just include both code parts into
e.g. (Range|Prefix|Wildcard)Query's rewrite() method. It would then be possible
to just switch the QueryParser or other code by e.g. setting a global (static)
flag in (Range|Prefix|Wildcard)Query that switches between both
implementations).
To your patch:
For printing out the boost in toString(): there is a nice helper routine
(instead of "if (getBoost()!=1.0f)...."). I think it should be consistent with
toString() of all other core query types.
> Add ConstantScorePrefixQuery and ConstantScoreWildcardQuery
> -----------------------------------------------------------
>
> Key: LUCENE-1424
> URL: https://issues.apache.org/jira/browse/LUCENE-1424
> Project: Lucene - Java
> Issue Type: New Feature
> Reporter: Mark Miller
> Assignee: Michael McCandless
> Priority: Minor
> Attachments: LUCENE-1424.patch
>
>
> If we want to be able to highlight these queries, they need to be added to
> Lucene core or contrib (solr's WildCardFilter can be used to create the
> ConstantScoreWildcardQuery). They are very useful anyway.
--
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]
