lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wolf Siberski <>
Subject Re: DO NOT REPLY [Bug 31841] - [PATCH] MultiSearcher problems with Similarity.docFreq()
Date Thu, 21 Apr 2005 09:06:14 GMT
Doug Cutting wrote:
> When we deprecate things we should ensure:
> 1. That, if they're removed, everything else should keep working.
> 2. That they should indicate what should be used instead.
> In we now have methods whose javadoc refers to 
> deprecated methods, which will be a problem if those deprecated methods 
> are removed.  These deprecated search methods also do not indicate what 
> folks should call instead.  
Yes, I was sloppy here.

> In each case applications should call a corresponding Searcher method.  
Here I don't agree completely and have another suggestion to resolve that
issue. The affected methods are low-level API methods anyway,
and even before their javadoc referred application developers to other already
and still existing Searcher methods. If someone really needed to call one of
these methods before, IMHO he should now create a weight and call the
corresponding new method.

While checking this I also found some other references to the deprecated
methods (mainly in javadoc comments), and replaced them accordingly.
A patch proposal is attached.


View raw message