lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery
Date Tue, 30 Jun 2009 09:28:18 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725539#action_12725539
] 

Simon Willnauer commented on LUCENE-1713:
-----------------------------------------

For an issue like this we should go for "commit without patch" to keep the history of the
classes. If you create a patch and apply it without useing svn copy && svn commit
you will loose history which is not worth it in this case. Just a hint.

simon

> 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
>             Fix For: 2.9
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message