Lucene 1.9.1 and mod_python issue

On Jun 14, 2006, at 3:24 PM, 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.

That's the kicker -- it works GREAT from the command line.
It only  
hangs inside of mod_python.

What if I code my analyzer in java and add it to the
PyLucene code  
and wrap it appropriately? That should get around this
issue, no?

--

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

Robert Kaye     --     robeorbit.net     --    http://mayhem-chaos.net


_______________________________________________
pylucene-dev mailing list
pylucene-devosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/pylu
cene-dev

On Wed, 14 Jun 2006, Robert Kaye wrote:

>
> On Jun 14, 2006, at 3:24 PM, 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.
>
> That's the kicker -- it works GREAT from the command
line. It only hangs 
> inside of mod_python.

If threading.currentThread() is not returning an instance of

PyLucene.PythonThread then this working great is pure luck.

> What if I code my analyzer in java and add it to the
PyLucene code and wrap 
> it appropriately? That should get around this issue,
no?

That can solve the PerFieldAnalyzerWrapper issue but not the
threading issue.
If the PerFieldAnalyzerWrapper extension is the proper Java
Lucene way to do 
things, it's probably easier for me to add support for that
under PyLucene.

Andi..
_______________________________________________
pylucene-dev mailing list
pylucene-devosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/pylu
cene-dev