[
https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726559#action_12726559
]
Uwe Schindler commented on LUCENE-1713:
---------------------------------------
After comparing the old 2.4.1 javadocs with the new ones, I found out, that
RangeQueries in 2.4.1 only had Term ctors and no (field,String,String) ctors.
As the new classes are separated (deprecated one and new one), I will change it
to not have this strange getLowerTermText methods in the new class.
So I will prepare a new patch and do all tests again, no commits for now. The
current patch had also some minor problems with BW compatibility and a missing
collator.
> Rename RangeQuery -> TermRangeQuery
> -----------------------------------
>
> Key: LUCENE-1713
> URL: https://issues.apache.org/jira/browse/LUCENE-1713
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.9
> Reporter: Michael McCandless
> Assignee: Uwe Schindler
> Fix For: 2.9
>
> Attachments: LUCENE-1713.patch, RangeFilter.java, RangeQuery.java
>
>
> Since we now have NumericRangeQuery (LUCENE-1701) we should rename RangeQuery
> to TextRangeQuery to make it clear that TextRangeQuery (TermRangeQuery?
> StringRangeQuery) is based entirely on text comparison.
> And, existing users on upgrading to 2.9 and using RangeQuery for [slow]
> numeric searching would realize they now have a good option for numeric range
> searching.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
