Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Groose, Brian" <Brian.Groose@ironmountain.com>
To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>
Date: Tue, 22 Feb 2011 18:46:54 -0500
Subject: ParallelReader and updateDocument don't play nice?
Thread-Topic: ParallelReader and updateDocument don't play nice?
Thread-Index: AcvS6sjgxHfhI/UYQxmJ6S57bgJSVQ==
Message-ID: <DC78AF06EBB33E47B8C8ED1214B33BF0CEC3F1C2ED@NUMEVP12.na.imtn.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="_000_DC78AF06EBB33E47B8C8ED1214B33BF0CEC3F1C2EDNUMEVP12naimt_"

--_000_DC78AF06EBB33E47B8C8ED1214B33BF0CEC3F1C2EDNUMEVP12naimt_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

I have been looking at using ParallelReader as its documentation indicates,=
 to allow certain fields to be updated while most of the fields will not be=
 updated.

However, this does not seem possible.  Let's say I have two indexes, A and =
B, which are used in a ParallelReader.  If I update a document in index B, =
then I must also update the same document in index A, otherwise the documen=
ts in the two indexes do not line up.  This kind of defeats the purpose of =
using two indexes with ParallelReader, since I could just use a single inde=
x and update the one document as usual, ParallelReader buys me nothing but =
more complexity.

Am I missing something here?  Is there some way to update a Document (or Fi=
eld) so that it won't actually be a delete+add?

It would seem that to update a single Document or Field in index B I really=
 need to fully re-index B with the documents in the same order, which gets =
expensive if you have tens of millions of documents in the index.

Thoughts?

Thanks!


The information contained in this email message and its attachments is inte=
nded only for the private and confidential use of the recipient(s) named ab=
ove, unless the sender expressly agrees otherwise. Transmission of email ov=
er the Internet is not a secure communications medium. If you are requestin=
g or have requested the transmittal of personal data, as defined in applica=
ble privacy laws by means of email or in an attachment to email, you must s=
elect a more secure alternate means of transmittal that supports your oblig=
ations to protect such personal data. If the reader of this message is not =
the intended recipient and/or you have received this email in error, you mu=
st take no action based on the information in this email and you are hereby=
 notified that any dissemination, misuse or copying or disclosure of this c=
ommunication is strictly prohibited. If you have received this communicatio=
n in error, please notify us immediately by email and delete the original m=
essage.=20
--_000_DC78AF06EBB33E47B8C8ED1214B33BF0CEC3F1C2EDNUMEVP12naimt_--