The only thing that Hits gives that I want without the expense (Hits is
expensive to use this way) is that you can do a search and get all of
the results back with sorting...sorting appears to be built into
TopDocs, so you don't get it with a HitCollector. If you try and use
TopDocs instead of hits then you need to know how many docs will
match...you do not have that info before doing the search...TopDocs
requires it though (for sorting and non sorting), to initialize its
priority queues to the correct size. Hits is also nice for normalizing
scores for you.
- Mark
Otis Gospodnetic wrote:
Heh, brave! :) I haven't used TopDocs enough to feel this strong against Hits
yet.
But while we are at it, what I think I really want is what Marvin does in
KinoSearch:
my $hits = $searcher->search( query => $query );
$hits->seek( $offset, $num_wanted );
This suits my experience and typical use of Lucene. I always know which "page"
of results I want, and how many matches I want to show per page, so I always know the
offset and always know how many matches after that offset I need. If I show 10 results
per page, and want to get a third page of results, ideally I'd do as little work as
possible for the first 20 matches, and just get the slice I need. Of course, I'll still
need to go through the first 20 and score them, but in the end I'll just throw them out.
Otis
----- Original Message ----
From: Nadav Har'El <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Sunday, November 26, 2006 3:07:26 AM
Subject: Re: Controlling Hits
On Fri, Nov 24, 2006, Otis Gospodnetic wrote about "Controlling Hits":
Hi,
Could we make Hits non-final, or at least expose something in Hits to control
the number of Documents it reads from disk?
...
Or maybe the answer is: Use the search method that returns TopDocs if you want
more control...?
In an application I was writing, I was facing similar issues: "Hits" was fine
for a short Demo in Lucene, but when it came to a real application, it didn't
give me enough control: it reran the search too many times when you wanted
to see, e.g, the 20th result page, and wouldn't allow me adding a HitCollector
which I needed. I started by modifying Hits (which wasn't just final - much
of its functionality was private), but then realized: there's simply no
reason to use Hits! IndexSearcher.search() which returns TopDocs already
gives you full control, and frankly isn't that much harder to use.
In fact, I fail to see a situation where "Hits"'s concept of "random access"
to the results (you can ask for result #30 and then #70) even makes sense.
In all search applications I'm familar with, at the time you call search(),
you already know how many results you want to display - and you don't need
someone to guess for you that you need 50 results, and if that's not enough
then you need 100 results, and then 200, and so on.
And since this concept of "random access" is what differenciates Hits from
TopDocs, perhaps we don't need Hits at all?
So, how about deprecating Hits altogether, and recommending the TopDocs
alternatives instead?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
