[EMAIL PROTECTED] wrote:
I am interested in pursuing experienced peoples' understanding as I have half the queue approach developed already.
well I think that experienced people developed lucene :) theyoffered us
the possibility to use multithreading and concurent searching.
Of course .. depen
I am interested in pursuing experienced peoples' understanding as I have half
the queue approach developed already.
I am not following why you don't like the queue approach Sergiu. From what I
gathered from this board, if you do lots of updates, the opening of the
WriterIndex is very intensiv
AIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Monday, November 15, 2004 5:50 PM
Subject: Re: Lucene : avoiding locking (incremental indexing)
It really seems like I am not the only person having this issue.
So far I am seeing 2 solutions and honestly I d
m with
large content directories.
As I learn more I plan to expand the functionality of my class.
Luke S
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Monday, November 15, 2004 5:50 PM
Subject: Re: Lucene : avoiding lo
On Mon, 2004-11-15 at 16:50, [EMAIL PROTECTED] wrote:
> So far I am seeing 2 solutions and honestly I don't love either totally. I
> am thinking that without changes to Lucene itself, the best "general" way to
> implement this might be to have a queue of changes and have Lucene work off
> this
pieces of the database rather then the whole
database. I think I need to look in the developer archives.
JohnE
- Original Message -
From: Luke Shannon <[EMAIL PROTECTED]>
Date: Monday, November 15, 2004 5:14 pm
Subject: Re: Lucene : avoiding locking (incremental indexing)
>
t;[EMAIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Monday, November 15, 2004 5:01 PM
Subject: Re: Lucene : avoiding locking (incremental indexing)
> This is how I implemented incremental indexing. If anyone sees anything
> wrong, please let me know.
&
This is how I implemented incremental indexing. If anyone sees anything
wrong, please let me know.
Our motivation is similar to John Eichel's. We have a digital asset
management system and when users update, delete or create a new asset,
they need to see their results immediately.
The most import
