L FROM YOUR SYSTEM AND DESTROY ANY COPIES.
>
>
>
> *From:* Michael McCandless [mailto:luc...@mikemccandless.com]
> *Sent:* Monday, August 22, 2016 4:38 PM
> *To:* Stuart Goldberg
> *Cc:* Lucene Users
>
> *Subject:* Re: Problems Refactoring a Lucene Index
>
>
>
AND DESTROY ANY COPIES.
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Monday, August 22, 2016 4:38 PM
To: Stuart Goldberg
Cc: Lucene Users
Subject: Re: Problems Refactoring a Lucene Index
The design is indeed trappy, and many users have hit the situation you have
E THIS
> E-MAIL FROM YOUR SYSTEM AND DESTROY ANY COPIES.
>
>
>
> *From:* Michael McCandless [mailto:luc...@mikemccandless.com]
> *Sent:* Monday, August 22, 2016 10:48 AM
> *To:* Lucene Users ; sgoldb...@fixflyer.com
> *Subject:* Re: Problems Refactoring a Lucene Index
&g
SENDER BY REPLY
EMAIL AND PLEASE DELETE THIS E-MAIL FROM YOUR SYSTEM AND DESTROY ANY COPIES.
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Monday, August 22, 2016 10:48 AM
To: Lucene Users ; sgoldb...@fixflyer.com
Subject: Re: Problems Refactoring a Lucene Index
This
This is unfortunately "by design": Lucene makes no guarantees that the
Document you retrieve from an IndexReader is precisely the same Document
you had indexed.
Lucene only preserves the metadata it needs for each field.
Your only recourse is to create a new Document using your application level
As our software goes through its lifecycle, we sometimes have to alter
existing Lucene indexes. The way I have done that in the past is to open the
existing index for reading, read each Document, modify it and write that
Document to a new index. At the end of the process, I delete the old index
and
