portions of the Lucene index.
-Original Message-
From: Thomas K. Burkholder [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 5:36 PM
To: java-user@lucene.apache.org
Subject: Re: Fast index traversal and update for stored field?
Hey, thanks for the quick reply.
I've considered
: Sounds like there's nothing out of the box to solve my problem; if
: I write something to update lucene indexes in place I'll follow up
: about it in here (don't know that I will though; building a new,
: narrower index is probably more expedient and will probably be fast
: enough for my
Yet another idea just occurred. Remember that documents in
Lucene do not all have to have the same field. So what if you had
a *very special document* in your index that contained only the
changing info? Perhaps in XML or even binary format? Then, updating
your index would only involve deleting
Hi there,
I'm using lucene to index and store entries from a database table for
ultimate retrieval as search results. This works fine. But I find
myself in the position of wanting to occasionally (daily-ish) bulk-
update a single, stored, non-indexed field in every document in the
If you search the mail archive for update in place (no quotes),
you'll find extensive discussions of this idea. Although you're
raising an interesting variant because you're talking about a non-
indexed field, so now I'm not sure those discussions are relevant.
I don't know of anyone who has
Hey, thanks for the quick reply.
I've considered using a secondary index just for this data but
thought I would look at storing the data in lucene first, since
ultimately this data gets transported to an outside system, and it's
a lot easier if there's only one thing to transfer. The
