Re: Modify Field.Index.NO to Field.Index.NOT_ANALYZED

Thanks Peter & Eric Agreed, this is a costly mistake, and hopefully others will not make this same mistake in the future. I will have to reindex as some of my fields are not stored. Regards Tommy On Fri, Nov 11, 2011 at 5:37 AM, Erick Erickson wrote: > In addition to Peter's comment, changing

Re: Modify Field.Index.NO to Field.Index.NOT_ANALYZED

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 d

Re: Modify Field.Index.NO to Field.Index.NOT_ANALYZED

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,

Modify Field.Index.NO to Field.Index.NOT_ANALYZED

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 p