Ah great that was the kind of stuff I was looking for.
Right now I have < 1000 results, so it won't kill me to use hits. I will
look into Hit Collection for my next release to fix that...
Erick Erickson wrote:
>
> Watch out though. By "hit' I assume you mean a Hits object. Iterating
> over
Watch out though. By "hit' I assume you mean a Hits object. Iterating
over a large result set with a Hits object can be very inefficient because
the query re-executes every 100 or so. Think about a HitCollector
instead.
Best
Erick.
On Sun, Jun 22, 2008 at 2:59 PM, Dr. Fish <[EMAIL PROTECTED]> w
Ah I think I got it
hit.getDocument().getField("CityID").stringValue() seems to be what I wanted
Thanks!
Dr. Fish wrote:
>
> I tried this first, and I was having trouble iterating over them.
>
>
> If I do something like this
>
> hit.getDocument().getField("CountryID").toString()
>
> I
I tried this first, and I was having trouble iterating over them.
If I do something like this
hit.getDocument().getField("CountryID").toString()
I get a big long BS object.. not just the result of my search.
I also tried messing with the tokenStreamValue(), and had the same result.
How do I
Hi Dr. Fish,
You could make just a single query with the broadest query possible - e.g.
bacon AND country:"united states"
and then iterate over all results, dividing them into your three buckets based
on the values of the other two fields.
Steve
On 06/22/2008 at 12:29 PM, Dr. Fish wrote:
>
