[ http://issues.apache.org/jira/browse/LUCENE-703?page=comments#action_12446267 ]
Mark Harwood commented on LUCENE-703:
-------------------------------------
In my opinion the positives of this change outweigh the negatives but is it worth consulting
the java-user mailing list and canvassing opinion before committing?
> Change QueryParser to use ConstantScoreRangeQuery in preference to RangeQuery by default
> ----------------------------------------------------------------------------------------
>
> Key: LUCENE-703
> URL: http://issues.apache.org/jira/browse/LUCENE-703
> Project: Lucene - Java
> Issue Type: Improvement
> Components: QueryParser
> Affects Versions: 2.1
> Reporter: Mark Harwood
> Priority: Minor
> Attachments: patch.diff
>
>
> Change to QueryParser to default to using new ConstantScoreRangeQuery in preference to
RangeQuery
> for range queries. This implementation is generally preferable because it
> a) Runs faster
> b) Does not have the scarcity of range terms unduly influence score
> c) avoids any "TooManyBooleanClauses" exception.
> However, if applications really need to use the old-fashioned RangeQuery and the above
> points are not required then the "useOldRangeQuery" property can be used to revert to
old behaviour.
> The patch includes extra Junit tests for this flag and all other Junit tests pass
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
|