thanks for your replies. i have two more questions.
You need to be really certain your own locking protects Lucene
properly. Specifically, no IndexReader can be created (restarted)
while a writer is open against the index, and, only one writer can be
open on the index at once (it sounds like you
"Antony Bowesman" <[EMAIL PROTECTED]> wrote:
> Michael McCandless wrote:
>
> >> Yes, I've disabled it currently while the new test runs. Let's see.
> >> I'll re-run the test a few more times and see if I can re-create the
> >> problem.
> >
> > OK let's see if that makes it go away! Hopefully
Michael McCandless wrote:
Yes, I've disabled it currently while the new test runs. Let's see.
I'll re-run the test a few more times and see if I can re-create the problem.
OK let's see if that makes it go away! Hopefully :)
I ran the tests several times over the weekend with no virus check
Just to add to the thoughtful responses from the others, it isn't really that
bad to do a new search each time. First, the later searches may likely be
"warm" searches and thus won't take as long as the first search; second, it's
the searcher.doc(docId) part that will likely hurt the most, but h
Efficient in your situation, maybe. Good for everybody? Probably not.
The key is exactly your use of the word "state". Personally, I do
NOT want the core search engine to be stateful, that brings a whole
raft of problems with it. And Lucene is a search engine, not a search
application.
I really d
It has no performance problem and works fine.
whenever you are going to access a document the searcher will load the
document from the index.
On 4/1/07, Mohsen Saboorian <[EMAIL PROTECTED]> wrote:
This is possible, but the problem here is performance. Why is it not
possible
to support paginati
This is possible, but the problem here is performance. Why is it not possible
to support pagination in a more efficient way? Suppose, a Searcher looks
through Documents and find the matching ones. Theoretically, it can stop
searching when the result hit number gets more than a threshold. Searcher
Mosen,
In order to support pagination, I wrapped the Hits is a class just like
java.sql.ResultSet
You can create a wrapper class and put the Hits in that and implement some
methods like next() prev() to forward and backward through the docuements.
Hope this help you.
--
Regards,
Mohammad
"Chris Hostetter" <[EMAIL PROTECTED]> wrote:
>
> : locks without upgrading to 2.1. Our application uses its own custom
> : locking mechanism, so that lucene locking is actually redundant. We
> : are currently using Lucene version 2.0.
>
> since before the 2.0.0 release there has been a static
> FS
