Antonello,
You are right,I think lucene indexsearcher will search the old
information if IndexWriter was not closed(I think lucene release the Lock
here),so I only add a few documents every time from buffer to implement index
"real time".
kai
发件人: [EMAIL PROTECTED] [mailto:[EMAIL PROT
mkjjyy
On 8/10/07, Askar Zaidi wrote:
Hey Guys,
I am trying to do something similar. Make the content search-able as
soon as
it is added to the website. The way it can work in my scenario is
that , I
create the Index for a every new user account created.
Then, whenever a new document is
Well, closing/opening an index is MUCH less expensive than
rebuilding the whole thing, so I don't understand part of your
statements
It *may* (but I haven't tried it) be possible to flush the writer rather
than
close/open it. But, you MUST close/reopen the reader you search with
even if flush
Kai,
The context I'm going to work with requires a continuous addition of
documents to the indexes, since it's user-driven content, and this
would require the content to be always up-to-date.
This is the problem I'm facing, since I cannot rebuild a 1Gb (at
least) index every time a user inserts a
Hey Guys,
I am trying to do something similar. Make the content search-able as soon as
it is added to the website. The way it can work in my scenario is that , I
create the Index for a every new user account created.
Then, whenever a new document is uploaded, its contents are added to the
users I
With Compass, indexing is linked to your database transaction, when
your object is persisted, it's indexed too.
All your questions are managed cleanly and silently by Compass, just
have a look to the source code if you don't wont to use this product.
M.
Le 10 août 07 à 12:24, Antonello Prove
