On Sun, Jun 28, 2015 at 1:30 AM, Selva Kumar <selva.kumar.at.w...@gmail.com> wrote: > it appears 4.x Filter and our custom implementation inherited Object's > hashcode and equals method. Obviously, this worked for us so far. Logical > equality might not be important in this case and likely to be expensive > given the nature of the custom filters. > > Just wanted to understand any changes are around the corner before I > override these methods in the custom filters. > > It seems in some sense Filter has already become a Query. So what does it > mean to rewrite filter using Query API? > Search would call take only query instead of combination of query and > filter?
Our long-term goal is to remove org.apache.lucene.Filter entirely. Rewriting a Filter using the Query API means that instead of extending Filter and implementing getDocIdSet, you would have to extend Query and implement createWeight or rewrite(IndexReader). Then this query would be used as a FILTER clause in a BooleanQuery instead of a Filter in a FilteredQuery. -- Adrien --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
