[pylucene-dev] Lucene 1.9.1 and mod_python issue
Robert Kaye
rob at eorbit.net
Wed Jun 14 15:17:35 PDT 2006
On Jun 14, 2006, at 3:11 PM, Andi Vajda wrote:
> Any python thread running in this process accessing PyLucene needs
> to be known to libgcj's garbage collector. In other words, any
> python thread using PyLucene code (which calls into libgcj) needs
> to be an instance of PyLucene.PythonThread which does the right
> thing in setting it up via libgcj.
But that doesn't really explain why this runs fine if I dont use my
own custom analyzer -- if I use StandardAnalyzer, everything works
just fine. Does StandardAnalyzer and carrying out a lucene search not
allocate any java memory?
> This question has been asked many times before on this list already
> but I don't remember seeing any more practical answer on how this
> is actually done.
Do you have any tips on where I should look to find more info?
Thanks!
--
--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