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
#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
This is not a defect:
<http://wiki.apache.org/lucene-java/LuceneFAQ#Does_Lucene_allow_searching_and_indexing_simultaneously.3F>.
> -Original Message-
> From: Justin [mailto:cry...@yahoo.com]
> Sent: Monday, October 04, 2010 2:03 PM
> To: java-user@lucene.apache.org
&
Hi all,
The JavaDocs do not appear to mention that only stored fields persist
IndexWriter.updateDocument. When opening new readers, from either
IndexWriter.getReader or IndexReader.open, neither TermDocs nor IndexSearcher
will find terms in fields which weren't stored.
Existing readers, howeve
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
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
I would like to make some updates to values within my large index. I
understand that I have to delete and re-insert each document to be
changed to do that. However I do have some large fields that are
unstored (only indexed and no, these are not the fields that I am
wanting to change), which means
: 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.
Hi all,
I would like to update a document as follows.
1) retrieve the document from an IndexReader/Searcher
2) delete the document
3) manipulate the document, that is remove and add fields
4) save the document using an IndexWriter
When I do this all fields that were indexed and/or tokenized but