Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of rcmuir@gmail.com designates
 209.85.160.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=CvGfT2XkSNWmBSdQ3TvkhW9nWfJKz3GIKan2i624B6+rmEyLsJu5lfYcHwIB+7Ygzh
         cX44e9MZn9BzONfZCQl8bxZ3YSOO7EJzCgGPUcz3Z4k5Dtgyhr6qhjTQLsfmx64vWCL6
         A3lPdfpW67Lz4GR3qlMdqA4qcI35W39ZTDzMo=
MIME-Version: 1.0
In-Reply-To: <8c4e68611002180342w642f44b2ud18d7dc7842a1d1@mail.gmail.com>
References: <f071061b1002160247n60b12fbdk5917f43ac478b6fa@mail.gmail.com>
	<8c4e68611002180342w642f44b2ud18d7dc7842a1d1@mail.gmail.com>
From: Robert Muir <rcmuir@gmail.com>
Date: Thu, 18 Feb 2010 08:20:03 -0500
Message-ID: <8f0ad1f31002180520s11b53ee0o8e8a8ead75597cfc@mail.gmail.com>
Subject: Re: questions on upgrading to 3.0: Version.LUCENE_* and
	Field.setOmitNorms()
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=00504502e2d8540b72047fdfd438

--00504502e2d8540b72047fdfd438
Content-Type: text/plain; charset=UTF-8

Only use LUCENE_CURRENT if you do not care about backwards compatibility at
all: e.g. you are perfectly happy re-indexing all data when you upgrade the
lucene jar file in future.

its not about relying on quirks in previous versions of lucene, its about
being compatible with changes in future versions, you set it to LUCENE_30 or
whatever so that you can upgrade to 3.1 jar, without reindexing.

On Thu, Feb 18, 2010 at 6:42 AM, Ian Lea <ian.lea@gmail.com> wrote:

>
> Unless you are relying on quirks in particular versions of lucene
> setting it to LUCENE_CURRENT is probably best.
>
>
-- 
Robert Muir
rcmuir@gmail.com

--00504502e2d8540b72047fdfd438--