RE: Updating documents with fields that aren't stored

presents a shapshot in time. It's just less costly to reopen. > -Original Message- > From: Justin [mailto:cry...@yahoo.com] > Sent: Monday, October 04, 2010 2:15 PM > To: java-user@lucene.apache.org > Subject: Re: Updating documents with fields that aren't stored

Re: Updating documents with fields that aren't stored

#getReader() - Original Message From: Steven A Rowe To: "java-user@lucene.apache.org" Sent: Mon, October 4, 2010 1:05:36 PM Subject: RE: Updating documents with fields that aren't stored This is not a defect: <http://wiki.apac

RE: Updating documents with fields that aren't stored

This is not a defect: . > -Original Message- > From: Justin [mailto:cry...@yahoo.com] > Sent: Monday, October 04, 2010 2:03 PM > To: java-user@lucene.apache.org > Subject: Updating doc

Re: Updating documents in index with some fields not stored

Chun Wei Ho wrote: (2) I understand Luke is able to reconstruct the field so that the document can be re-inserted. Can someone give me a hint on how its done and if its potentially too time consuming for a large index (up to million docs and too many terms to count). Ah, I forgot to mention: wh

Re: Updating documents in index with some fields not stored

Chun Wei Ho wrote: (2) I understand Luke is able to reconstruct the field so that the document can be re-inserted. Can someone give me a hint on how its done and if its potentially too time consuming for a large index (up to million docs and too many terms to count). Luke simply iterates over a

Re: Updating documents

: When I do this all fields that were indexed and/or tokenized but not : stored get lost. : : So is there any way to preserve fields that were not stored? : Reconstructing these fields is to expensive in my application. "preserving" those fields is pretty much the oposite of "not storing" them.