Yep. What I've done is hack a little class to pool the searchers, and whenever
I update the index, I inform this manager class, and it refreshes the
searchers. Of course, you can add sugar on top of that, like specifying a TTL
or something like that.
Kelvin
On Tue, 19 Aug 2003 13:18:24 -0500, Sco
Hi all!
I am working with Lucene 1.3 RC1 and found what I think is a problem.
Basically, I am indexing into a RAMDirectory and then using addIndexes to
merge the RAMDirectory into a file system index. Adding in a small
number of documents doesn't seem to work.
My test code is like this:
Hi. I'm using lucene 1.2 on a linux 2.4.18 kernel and I just did a quick
profile of lucene using runhprof under jdk1.3.1, and found that nearly 25%
of the cpu time was going towards an exception that I didn't even know
existed. Lucene appears to be swallowing whatever it is because I'm not
seeing
Why do you have concurency problems? are you trying to
have each user initiate the indexing himself? because
that will create issues, how about you put all the new
files you want to index in a directory and then have a
schedule procedure on the webserver run the lucene
indexer on that directory, ou
Yes. You can (and should for best performance) reuse an IndexSearcher
as long as you don't need access to changes made to the index. An open
IndexSearcher won't pick up changes to the index, so if you need to see
the changes, you will need to open a new searcher at that point.
Scott
Aviran M
HI,
> From: Dan Quaroni [mailto:[EMAIL PROTECTED]
>
> My index grew about 7 gigs larger than I projected it would,
> and it ran out of disk space during optimize. Does lucene
> have transactions or anything that would prevent this from
> corrupting an index, or do I need to generate the inde
Also the performance drops down a lot in my case for option 1
Regards,
Hui
- Original Message -
From: "Scott Ganyo" <[EMAIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Monday, August 18, 2003 3:03 PM
Subject: Re: Make Lucene Index distributable
> Be careful with option
Can I reuse one Instance of IndexSearcher to do multiple searches (in
multiple threads) or do I have to instantiate a new IndexSearcher for
each search?
My index grew about 7 gigs larger than I projected it would, and it ran out
of disk space during optimize. Does lucene have transactions or anything
that would prevent this from corrupting an index, or do I need to generate
the index again?
Thanks!
---
Hello,
I developed an Client-Server application on the web, with a search
module using Lucene. In the same application, the users can index new
text.
So, multiple sessions can acces to the Index and concurrences problems
can be possible.
I used Threads in Java. Is it the best solutions?
I
Hi Peter,
I guess you are right.
I've implemented this for a index with ten millions of really small
documents that all are stored in the index. The documents are never more
than a thousand
words so re-indexing is quick enough. However it is probably not
advisable to do
this with bigger documen
Hi Magnus,
thanks for the offer, but unfortunately I can't/don't want to make the
assumption that I can easily access the documents to re-index them. And
I don't think this approach would be feasible unless you can keep the
documents in memory somehow.
Storing the other/non-inverted/normal/wha
Ok, here it is. It's part of a JSP that prints out all keywords in a
document.
/magnus
<%@ page import="org.apache.lucene.index.IndexReader,
org.apache.lucene.document.Document,
com.technohuman.search.language.SwedishAnalyzer,
java.io.StringReader,
hello magnus,
can i ask your sample script?
--buics
Hi Peter
If the original document is available. You could extract keywords from
the document
at query time. That is when someone asks for documents similar to
document a. You
re-analyze document a and in combination with statistics from t
Hi Peter
If the original document is available. You could extract keywords from
the document
at query time. That is when someone asks for documents similar to
document a. You
re-analyze document a and in combination with statistics from the Lucene
index you extract
keywords from document a that
15 matches
Mail list logo