lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Willnauer <>
Subject Re: Having a default constructor in Analyzers
Date Mon, 08 Feb 2010 08:48:04 GMT
On Mon, Feb 8, 2010 at 9:31 AM, Sanne Grinovero
<> wrote:
> 2010/2/8 Robert Muir <>:
> ---->8 snip 8<----
>> how would this work when the Query analyzer differs from the Index analyzer?
>> For example, using commongrams in solr means you use a different Query
>> analyzer from Index analyzer, and there are some other use cases even in
>> solr (synonyms expansion and things like that)
> ---->8 snip 8<----
> They are two different Analyzer types, but I assume they want to use
> the same value for Version, right? The same version which was used to
> build the rest of the index.
So this is trick, if you have Analyzer A(Version.1) and Analyzer
B(Version.2) and build an index with it you will likely have to
maintain those version until you make a clean cut and upgrade to
A(Version.X) B(Version.X). If you are upgrading to 2.9 from 2.x you
can simply use Version.2.x for both of you analyzers. It always
depends on the changes which have been applied to the Analyzers but it
is very likely that they break your index compat if you blindly

One of the biggest problems is that some of your users might want to
use analyzer X with Version.Y and analyzer X' with Version.Y' because
of some weird "buggy" behavior. You have to find your way through this
unfortunately. You might offer your users to define the versions
themselves and warn them like Robert did in the blinking JavaDoc :)

> Regards,
> Sanne
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message