lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Muir <>
Subject Re: questions on upgrading to 3.0: Version.LUCENE_* and Field.setOmitNorms()
Date Thu, 18 Feb 2010 13:20:03 GMT
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 <> wrote:

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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message