lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <>
Subject BooleanQuery.equals
Date Mon, 28 Feb 2005 19:49:13 GMT
I'm working on a BooleanQuery subclass for a contract job, and when 
using JUnit to compare an expected query with an actual query it was 
failing even though the queries (clauses and boost) were all identical.

Instead of using == in BooleanQuery.equals to compare the clause array, 
it should be Arrays.equals(this.getClauses(), other.getClauses()).  
Arrays.equals is a JDK 1.2+ method.  Any objections to switching 
BooleanQuery's .equals implementation accordingly?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message