On Oct 3, 2009, at 9:23 PM, Mark Miller wrote:
Gotchya - that clears up my mind. I know your an advanced user, so it
threw me for a loop that you would be using Hits like a Collector.
Just
have been seeing that a lot lately.
Is there enough interest to add a new search method? (Hiterator?
Gotchya - that clears up my mind. I know your an advanced user, so it
threw me for a loop that you would be using Hits like a Collector. Just
have been seeing that a lot lately.
Just read to much into: So what is the appropriate documentation for
getting all "hits"?
Another option (of course) is
It makes sense if you understand the context. We make each verse of a
Bible a document. There are about 36000 docc in a Bible. We want a
user to find all the verses that match there search to give the count
of total hits. We then show slices of the hits from first hit to last
im document or
I think it could be reworded as well - its kind of uhh ... but I'll
leave that to someone else if they care. For now I just pointed it to
the correct method.
Mark Miller wrote:
> You used Hits to get all that hits? Nasty man - thats we deprecated that
> class - even though the JavaDoc warns you th
You used Hits to get all that hits? Nasty man - thats we deprecated that
class - even though the JavaDoc warns you thats a major speed trap,
everyone still did it ... use a Collector.
Your right though - it shouldn't point to IndexSearcher.search(Query)
after that - it should point to IndexSearche
Writing a Collector is the correct and fastest way to do this. The Javadoc
pointing to deprec API is incorrect.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
_
From: DM Smith [mailto:dmsmith...@gmail.com]
Sent: Sunday, October 04
