Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of serera@gmail.com designates
 72.14.220.154 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=WM3yf5TTc15xwJzRBh8kte0HHG4R+bFPJpKCtmUm+i7Fg+ujjdpQmlfFXiFx6gg20F
         CWijXsWUA6tmipdb4UJNjIPVQyXaWZVo/LQHTqjqv8s8VWz3NbHUQLXgNak9MPdZ5Hyj
         /OAP1foJgyAtvqeu1fQ4vf6jA0V+mcOmC8750=
MIME-Version: 1.0
In-Reply-To: <4BC38D03.9020202@jobdiva.com>
References: <4BC38D03.9020202@jobdiva.com>
Date: Tue, 13 Apr 2010 08:41:22 +0300
Message-ID: <t2v786fde51004122241s77a61e28s9772243f2214b146@mail.gmail.com>
Subject: Re: WhitespaceAnalyzer and version
From: Shai Erera <serera@gmail.com>
To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

WhitespaceAnalyzer definitely has a Version dependent ctor. What
Lucene version do you use?

You van use LUCENE_CURRENT but be aware that of a certain Analyzer's
behavior has changed in a way that affects your app, you'll need to
reindex your data. Usually an Analyzer (or any other Version-aware
object) documents the differences between the versions. Some classes
take Version as a placeholder for future changes, while not doing
anything special w/ them st the moment.

It is best, I think, if you stick w/ a specific version (like
LUCENE_30) and change that before you plan to reindex your data.
Otherwise, if you always reindex your stuff when upgrading Lucene,
then LUCENE_CURRENT is probably good.

Note also that some changes between versions may result on you
updating your users (manual) about what to expext from searches.

Hope this helps,
Shai

On Tuesday, April 13, 2010, Siraj Haider <siraj@jobdiva.com> wrote:
> We are in the process of removing the deprecated api from our code to mov=
e to version. =A0One of the deprecation is, the queryparser now expects a v=
ersion parameter in the constructor. =A0I also have read somewhere that we =
should pass the same version to analyzer when indexing as wel as when searc=
hing. =A0We use WhitespaceAnalyzer and I am unable to find a constructor wi=
th a version in it.
>
> Another thing is, do we need to re-index if we want to supply Version.LUC=
ENE_CURRENT as the version? what are other implications?
>
> thanks
> -siraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

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