Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 carlton@sumologic.com does not designate 209.85.216.176 as permitted sender)
MIME-Version: 1.0
Date: Thu, 19 Jan 2012 11:01:39 -0800
Message-ID: 
 <CAOLuRY36pDXBdt_vin16eX=nER_c66OO9HonfvQUV+n=9T0-mA@mail.gmail.com>
Subject: any tips for upgrading Lucene 3.0.3 -> 3.5.0?
From: David Carlton <carlton@sumologic.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=20cf30334973b947f604b6e6312a

--20cf30334973b947f604b6e6312a
Content-Type: text/plain; charset=ISO-8859-1

I'm hoping to upgrade Lucene on a local code base from 3.0.3 to 3.5.0; is
there a good guide out there for particular pitfalls that I should worry
about? I've skimmed the ChangeLogs; the mention of an index upgrade tool
made me wonder: has the index format changed between those versions? If so,
what's the best way to handle that without reindexing?  (I was assuming
that I'd be able to be careful about where I pass in VERSION_30 and where I
pass in VERSION_35, but looking through the current code, there actually
are basically no non-test situations where we pass in a version number at
all - e.g. we only use QueryParser for test code - so maybe I don't have to
worry about incompatibilities?) Any other gotchas that won't be obvious
from compilation failures and straightforward sanity check test failures?
(We do have tests that run basic queries on sample input.) Are there
intermediate versions that we should try, e.g. 3.0.3 -> 3.4.0 -> 3.5.0
instead of going straight from 3.0.3 to 3.5.0?

If it matters: the one unusual Lucene usage that we have is that we've
written our own Tokenizer.

Thanks for any pointers that people have.

-- 
David Carlton
carlton@sumologic.com

--20cf30334973b947f604b6e6312a--