[KinoSearch] kinosearch 0.20 usable?

Peter Karman peter at peknet.com
Sat Feb 7 05:56:53 PST 2009


Gert Brinkmann wrote on 2/7/09 5:04 AM:
> Andrew Bramble wrote:
> 
>> If utf8 is a big concern you might cheat with a modified
>> analyzer/encoding in the index and fetch your real utf8 data from
>> _other_ storage via document key field ? or store encoded in an
>> unanalyzed field then decode on fetch.
> 
> AFAIU this would mean that we had to do some things as e.g. highlighting 
> on our own. Maybe this was possible, but it does not sound as a very 
> robust, performant and simple solution. Also a question is if all the 
> other things in the search engine could handle utf-8 (Umlauts, etc.).
> 

I have not tried it yet, but I expect you could use Search::Tools with
KinoSearch for snipping and highlighting. It won't be as fast, since it uses a
regex for matching instead of start/end byte positions, but it should be
accurate at least.


-- 
Peter Karman  .  http://peknet.com/  .  peter at peknet.com




More information about the kinosearch mailing list