lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Modify Field.Index.NO to Field.Index.NOT_ANALYZED
Date Fri, 11 Nov 2011 13:37:02 GMT
In addition to Peter's comment, changing future documents to
Field.index.NOT_ANALYZED won't affect your current documents.

If (and only if) you stored all your data, you could conceivably
read through your entire index and re-index into another
location and have your PK available. *BUT* the only data you
have available to put in your new documents is in fields for
which Field.Store.YES was specified, fields that were
indexed-only don't have any way to recover the original
data that isn't lossy.


On Fri, Nov 11, 2011 at 12:38 AM, ppp c <> wrote:
> terrible.
> you have made a big mistake, since you in fact made the primary key
> unsearchable.
> There is no any other method, since deleteDocument, updateDocument both
> need Term to be searchable.
> The only way is during the traversal of all the docs and finding the
> matched field and delete it.
> On Fri, Nov 11, 2011 at 12:37 PM, Thanh Ha <> wrote:
>> I indexed my document using Field.Index.NO as the field index type, so
>> now I cannot search it to make updates.
>> Here's how the document was added:
>> Document doc = new Document();
>> doc.add(new Field("content_id", "1234", Field.Store.YES,
>> Field.Index.NO,  Field.TermVector.NO));
>> The content_id is the primary key for my documents.
>> Using updateDocument(Term,doc) won't work because the field must be
>> indexed in order to match (?).
>> Since I did store the value, is it possible to update this field index
>> type to Field.Index.NOT_ANALYZED ?
>> It will be very difficult to reindex, so any feedback is appreciated.
>> Thanks,
>> Tommy
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message