[pylucene-dev] Lucene 1.9.1 and mod_python issue

Robert Kaye rob at eorbit.net
Wed Jun 14 15:40:23 PDT 2006


On Jun 14, 2006, at 3:28 PM, Andi Vajda wrote:

>
> On Wed, 14 Jun 2006, Andi Vajda wrote:
>
>> In order to debug the actual crasher, or hang, it would helpful to  
>> first isolate the problem by running it in a regular python  
>> process instead of inside apache/mod_python.
>
> Then, if I understand what the PerFieldAnalyzerWrapper is for

It applies different analyzers to different fields in your document.  
In my case I have some fields that contain identifiers that I want to  
search for unchanged, and thus I want to use the KeywordAnalyzer. The  
rest of the fields should be analyzed with the default analyzer that  
I created.

> and the extension you're making is the correct Lucene way to do  
> this, I can add support for extending this class as a PyLucene  
> extension point. I don't think it's currently supported in PyLucene.

My custom analyzer is nothing fancy -- its a simple analyzer with  
unaccent filtering. But, I don't know if I am doing it correctly.

--

--ruaok      Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye     --     rob at eorbit.net     --    http://mayhem-chaos.net




More information about the pylucene-dev mailing list