Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44EEDE14.7090504@mikemccandless.com>
Date: Fri, 25 Aug 2006 07:25:08 -0400
From: Michael McCandless <lucene@mikemccandless.com>
User-Agent: Thunderbird 2.0a1 (X11/20060724)
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: Re: Upgrade from 1.4.3 to 1.9.1. Any problems with using existing
 index files?
References: <44EE98FC.7070505@atlassian.com>
In-Reply-To: <44EE98FC.7070505@atlassian.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


> We are upgrading from Lucene 1.4.3 to 1.9.1, and have many customers 
> with large existing index files. In our testing we have reused large 
> indexes created in 1.4.3 in 1.9.1 without incident. We have looked 
> through the changelog and the code and can't see any reason there should 
> be any problems doing so.
> 
> So, we're just wondering, has anyone had any problems, or is there 
> anything we need to look out for?

Looking at the code and also at the file formats specification:

   http://lucene.apache.org/java/docs/fileformats.html

I believe this is completely fine.  Meaning, the 1.9.x code can open the 
older index format for both searching and writing (either deletes or 
added docs), without issue.

Mike

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