[
https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1713:
----------------------------------
Attachment: RangeQuery.java
LUCENE-1713-backwards-branch.patch
LUCENE-1713.patch
New patch for reference (before all Range* must be svn renamed to TermRange*):
- Restores original API of RangeQuery and RangeFilter (the backards-tag must be
changed to use the original 2.4 tests, see java-dev-mail from me regarding this)
- RangeQuery is a deprecated dummy class deleagting everything to
TermRangeQuery, but is not a subclass, because different semantics of ctors and
some getter methods.
- new classes use cleaner API (no such strange methods like getLowerTermText()
because of overriding)
> 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-backwards-branch.patch, LUCENE-1713.patch,
> LUCENE-1713.patch, RangeFilter.java, RangeFilter.java, RangeQuery.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
