lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <e...@ehatchersolutions.com>
Subject Re: 1.4.3 breaks 1.4.1 QueryParser functionality
Date Wed, 05 Jan 2005 10:04:42 GMT

On Jan 4, 2005, at 9:43 PM, Bill Janssen wrote:
> Let me be a bit more explicit.  My method (essentially an
> after-method, for those Lisp'rs out there) begins thusly:
>
>     protected Query getFieldQuery (String field,
> 				   Analyzer a,
>                                    String queryText)
>         throws ParseException {
>
>           Query x = super.getFieldQuery(field, a, queryText);
>
> 	  ...
> 	}
>
> If I remove the "Analyzer a" from both the signature and the super
> call, the super call won't compile because that method isn't in the
> QueryParser in 1.4.1.  But my getFieldQuery() method won't even be
> called in 1.4.1, because it doesn't exist in that version of the
> QueryParser.

Will it work if you override this method also?

protected Query getFieldQuery(String field,
                               Analyzer analyzer,
                               String queryText,
                               int slop)

My head is spinning looking at all the various signatures of this 
method we have and trying to backtrack where things went awry.

	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org


Mime
View raw message