Hi Selva, Indeed, this default implementation is not good enough for most filters and should be extended in order to include parameters that define the "identity" of the filter. One could argue that using object identity might be a better default, but since Filter now extends Query it also needs to implement clone() in such a way that a clone of a filter is equal to the original filter, which would never work when using object identity by default for equals.
If you have custom filters, I would encourage you to rewrite them using the query API instead of Filter. On Sat, Jun 27, 2015 at 2:38 AM, Selva Kumar <selva.kumar.at.w...@gmail.com> wrote: > With Query/Filter merger, it appears default Filter hashcode() varies by > class, not object instance. Different object instances could have same > value. Am I missing something? -- Adrien --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
