On Wed, Jul 11, 2007 at 04:12:35PM +0200, Andreas Korth wrote: > > On 11.07.2007, at 15:40, Andreas Korth wrote: > > > Turns out there is a problem with a custom analyzer of mine. It works > > OK and passed all tests but it seems that Ferret isn't using the same > > analyzer for searching and indexing although I've arranged for it. Or > > so I thought. > > Here are three more questions related to the problem. The problem is > definitely an analyzer mismatch but I can't really put my finger on it. > > 1. Is it required to pass the field_infos everytime the index is > opened, or is it sufficient if the index is once created via > FieldInfos#create_index? In other words: are the field infos stored > in the index?
yes. > 2. The analyzer to be used for both reading and writing is passed to > Index.new() via the :analyzer parameter. Correct? This is what I do > and I even set the analyzer explicitly using Index#add_document(doc, > analyzer). correct. > 3. For a given Index, how can I determine which analyzer is currently > used for any given field, both for reading and writing? I don't know any way to get this information. You can use process_query to see what the query parser generates from your query string (which involves analyzing it). To see what gets indexed, you could use the ferret_browser Dave introduced with the latest release to inspect your index. 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
