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
[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 ..
I am new to Lucene, but have a large project in production on the web using
other apache software including Tomcat, Struts, OJB, and others.
The database I need to support will hopefully grow to millions of records.
Right now it only has thousands but it is growing. These documents get
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
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)
Hi Luke;
I have a similar system (except
[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 don't love either totally.
I am thinking that without changes
.
- Original Message -
From: [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 6:56 PM
Subject: Re: Lucene : avoiding locking
I'm working on a similar project...
Make sure that only one call to the index method is occuring at
a time
Francl [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Friday, November 12, 2004 10:38 AM
Subject: Re: Lucene : avoiding locking
Luke,
I also integrated Lucene into a content management application with
incremental updates and ran into the same problem you did.
You need
PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Friday, November 12, 2004 10:38 AM
Subject: Re: Lucene : avoiding locking
Luke,
I also integrated Lucene into a content management application with
incremental updates and ran into the same problem you did.
You need to make
On Fri, 2004-11-12 at 09:51, Luke Shannon wrote:
Hi Luke;
Currently I am experimenting with checking if the index is lock using
IndexReader.locked before creating a writer. If this turns out to be the
case I was thinking of just unlocking the file.
Do you think this is a good strategy?
.
- Original Message -
From: [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 6:56 PM
Subject: Re: Lucene : avoiding locking
I'm working on a similar project...
Make sure that only one call to the index method is occuring at
a time
();
}
}
}
- Original Message -
From: Otis Gospodnetic [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Friday, November 12, 2004 11:03 AM
Subject: Re: Lucene : avoiding locking
Hello,
--- Luke Shannon [EMAIL PROTECTED] wrote:
Currently I am experimenting
Hi All;
I have hit a snag in my Lucene integration and don't know what to do.
My company has a content management product. Each time someone changes the
directory structure or a file with in it that portion of the site needs to
be re-indexed so the changes are reflected in future searches
I'm working on a similar project...
Make sure that only one call to the index method is occuring at
a time. Synchronizing that method should do it.
--- Luke Shannon [EMAIL PROTECTED] wrote:
Hi All;
I have hit a snag in my Lucene integration and don't know what
to do.
My company has a
I will try that now.
Thank you.
- Original Message -
From: [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 6:56 PM
Subject: Re: Lucene : avoiding locking
I'm working on a similar project...
Make sure that only one call to the index method
PROTECTED]
Sent: Thursday, November 11, 2004 6:56 PM
Subject: Re: Lucene : avoiding locking
I'm working on a similar project...
Make sure that only one call to the index method is occuring at
a time. Synchronizing that method should do it.
--- Luke Shannon [EMAIL PROTECTED] wrote:
Hi All;
I
16 matches
Mail list logo
