Hello, Andi. AV> On Wed, 12 Jul 2006, Yura Smolsky wrote:
>> Hello, Andi. >> >> AV> On Wed, 12 Jul 2006, Yura Smolsky wrote: >> >>>> AV> Maybe the index was already optimized ? >>>> >>>> it was not optimized. is there incapability between old version of >>>> Lucene and new one? >> >> AV> If there is it should be just as with Java Lucene. >> AV> My understanding is that Lucene 2.0 should be able to read 1.4.3 indexes. >> AV> I'm not sure it should be able to write them. To find out for sure, you >> should >> AV> ask [email protected] >> >> Actually Lucene (java) optimized it fine. And PyLucene does not want >> to perform any changes at all on the same index. Index is huge (40Gb) >> so I cannot pack it and send to you :) I will try to reproduce this >> thing on a smaller one. AV> Maybe the process is failing silently ? i have checked it by adding some operators after optimize(). they are executed. AV> What version of gcj did you use to build PyLucene ? AV> There are file size limits (2 or 4 gb) with gcj < 4.x gcj (GCC) 4.0.3 BTW, I cannot read index using PyLucene 1.4.3 which was built with PyLucene 2.0.0. It raise Out Of Boundary exception. Is it normal? -- Yura Smolsky, http://altervisionmedia.com/ _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
