tcher" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, September 06, 2006 5:09 PM
Subject: Re: Keep hits in results
>
> On Sep 6, 2006, at 4:41 AM, jacky wrote:
>
> > Erik, thanks!
> >You are right! It is not a good idea to hold on a hits since the
> > index
On Sep 6, 2006, at 4:41 AM, jacky wrote:
Erik, thanks!
You are right! It is not a good idea to hold on a hits since the
index will be updated.
So, when i keep a hits, and then the index is updated, the searcher
will be auto-updated,too. rigtht?
No, Lucene itself has no "auto-update" of
;Erik Hatcher" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, September 06, 2006 4:15 PM
Subject: Re: Keep hits in results
On Sep 6, 2006, at 12:56 AM, jacky wrote:
> hi,
> The following words are quoted from "lucene in action":
> "There are a couple of implementa
On Sep 6, 2006, at 12:56 AM, jacky wrote:
hi,
The following words are quoted from "lucene in action":
"There are a couple of implementation approaches:
1. Keep the original Hits and IndexSearcher instances available
while the
user is navigating the search results.
2. Requery each time
whenever you want, and
> the performance
> will be better, right? (Don't think about state of users in webapp
> for a while)
>
> Best Regards.
>jacky
>
> - Original Message -
> From: "Doron Cohen" <[EMAIL PROTECTED]>
> To:
> Sen
AIL PROTECTED]>
To:
Sent: Wednesday, September 06, 2006 2:06 PM
Subject: Re: Keep hits in results
> Hits is not really a simple container - it references a certain searcher -
> that same searcher that was used to find these hits. When a request for a
> result document is made, the Hits
Hits is not really a simple container - it references a certain searcher -
that same searcher that was used to find these hits. When a request for a
result document is made, the Hits object delegates this request to the
searcher. So in order to "page through" the results using an existing Hits
obje
hi,
The following words are quoted from "lucene in action":
"There are a couple of implementation approaches:
1. Keep the original Hits and IndexSearcher instances available while the
user is navigating the search results.
2. Requery each time the user navigates to a new page.
It turns out th
