On Fri, May 04, 2007 at 12:34:38AM +0200, Danny Burkes wrote: > Hi- > > I was previously using 0.11.4, and I wrote my own analyzer. Everything > worked fine. > > When I took the system to production, 0.11.4 starting failing updating > the index, complaining that files were missing. The failure always > happened on the same model document, and was completely reproducible. > This failure looked a lot like the one described at > http://www.ruby-forum.com/topic/104145.
Bad you still have this problem. Did you try to run Ferret's unit tests on that Mac? > I reverted to 0.11.3, and all my model documents index fine (over 3M > documents). However, as I later found out, my custom analyzer was > returning bogus data, so the index as currently built is useless. > > What I observe is that, if I specify a custom analyzer using the > :analyzer option to acts_as_ferret, the calls to my custom analyzer are > fine when using Ferret 0.11.4. However, when I reverted back to 0.11.3, > calls to my analyzer's token_stream method always have a blank string. > That is, the "input" parameter to > http://ferret.davebalmain.com/api/classes/Ferret/Analysis/Analyzer.html#M000324 > is always a blank string. The field_name parameter is correct for both > 0.11.4 and 0.11.3. There was a conversation about this issue here right before 0.11.4 was released, where Dave explains what is happening: http://www.ruby-forum.com/topic/103004#231032 I'm not sure but maybe with the help of that posting you could change your analyzer to work with 0.11.3... jens -- Jens Krämer webit! Gesellschaft für neue Medien mbH Schnorrstraße 76 | 01069 Dresden Telefon +49 351 46766-0 | Telefax +49 351 46766-66 [EMAIL PROTECTED] | www.webit.de Amtsgericht Dresden | HRB 15422 GF Sven Haubold, Hagen Malessa _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
