Issue Type: Bug Created: 2006-06-21T10:18:07.000+0000 Last Updated: 2009-01-20T10:07:32.000+0000 Status: Resolved Fix version(s): - 0.2.0 (29/Oct/06)
Reporter: Alexander Veremyev (alexander) Assignee: Alexander Veremyev (alexander) Tags: - Zend_Search_Lucene
Related issues: - ZF-87
Attachments: - lucene-64bit.diff
In playing around with the Lucene_Search tool, I ran into a PHP Fatal error when trying to load large amounts of data (actually, not all that much data, but around 200,000 varchar(100) text fields): PHP FATAL ERROR: Allowed memory size of 104857600 bytes exhausted (tried to allocated 119 bytes) in Zend/Search/Lucene/Analysis/Analyzer/Common/Text.php on line 65. and PHP FATAL ERROR: Allowed memory size of 104857600 bytes exhausted (tried to allocated 64 bytes) in Zend/Search/Lucene/Index/SegmentWriter.php on line 480.
I am curios if there are any known restrictions on the amount of data you can use when building the Lucene search documents?
Posted by Alexander Veremyev (alexander) on 2006-06-21T10:31:27.000+0000
It depends from segment merging functionality.
addDocument() accumulates documents in memory and writes down new segment only at commit() time.
Frequent commits make index segments small and non-optimal. Take a look on a http://framework.zend.com/manual/en/…
Segment merging functionality will allow make index optimization automatically.
Posted by Alexander Veremyev (alexander) on 2006-10-08T19:53:17.000+0000
Done. MergeFactor, MaxMergeDocs and MaxBufferedDocs index options define auto-optimization behaviour.
Posted by Piotr Gabryjeluk (gabrys) on 2009-01-20T10:05:19.000+0000
This is patch that hopefully fixes Zend_Search_Lucene for 64bit systems. It seems that it is a reverse patch.
Posted by Piotr Gabryjeluk (gabrys) on 2009-01-20T10:07:32.000+0000
I'm sorry about attaching a patch file in wrong place. The right place is here http://framework.zend.com/issues/browse/ZF-4071
Have you found an issue?
See the Overview section for more details.