lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <>
Subject Re: 1.4.3 breaks 1.4.1 QueryParser functionality
Date Tue, 04 Jan 2005 21:12:14 GMT

If we broken API compatibility then we screwed up.  What getFieldQuery 
signature are you overriding?

As for version numbers - there are no strict conventions.  The API 
should not have broken in 1.4.2, nor in 1.4.3 - this is very 
unfortunate.  I caught what I thought were all of the incompatibilities 
introduced in 1.4.2, but apparently I missed something that perhaps my 
test cases didn't account for?


On Jan 4, 2005, at 1:13 PM, Bill Janssen wrote:

> I'm trying to figure out what changed between 1.4.1 and 1.4.3 to break
> my application.  I couldn't use 1.4.2, because my app wouldn't compile
> with 1.4.2, due to API changes.  With 1.4.3, the API incompatibilities
> were fixed, but now the QueryParser seems to process query strings
> differently.
> For instance, with 1.4.1, when I use the query string
>     category:"user names"
> during the parsing of the query, the method "getFieldQuery" is called,
> which allows me to do some custom analysis of the search terms, for
> particular field names.  However, with 1.4.3, "getFieldQuery" is *not*
> called.  Why not?  Is something else called instead?
> Also, what's the difference between major, minor, and micro release
> numbers in the context of the Lucene project?  I'm still stuck on
> 1.4.1 due to these incompatibilities.  I'm a bit surprised that
> differences between two micro releases of the same minor release would
> cause this much difficulty.
> Bill
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message