[KinoSearch] Field-specific terms vs. query filter?

[Larry Leszczynski]

Hey Marvin -

>> Is there any advantage to building up a Boolean query for just the 
>> category_id parts, and using that as a query filter instead?  I won't 
>> necessarily be able to cache/reuse the query filter.
>
> There shouldn't be much difference if any between the filtering approach and 
> the complex-query approach.  You have to build up the same data either way; 
> the QueryFilter just executes the "excluded" parts of the search first and 
> stuffs the result into a BitVector, then applies that to the "required" part.
>
> If you were able to keep the QueryFilter objects around, then on subsequent 
> searches, you wouldn't have to re-run the excluded parts of the search, but 
> oh well.  If the box you're running this on has sufficient memory, the kernel 
> cache will probably help you out behind the scenes.

I figured that might be the case, thanks much for the info.


>> Related question:  Assuming the category_id field is indexed but not 
>> analyzed, is a field-specific term going to do an exact match?  I.e. will 
>> "category_id:1" match just "1", or will it also match "10"?
>
> It will do an exact match.

Cool.  Is there any syntax to query an analyzed field for an exact 
match?  E.g. if I want to match "cream" but not "creamy"?


Larry


_______________________________________________
KinoSearch mailing list
KinoSearch at rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch