I believe the problem was in how I was creating my index. My acts_as_ferret
declaration was as follows:
acts_as_ferret( :fields => {
:name => {},
:desc => {:index => :untokenized_omit_norms},
:body => {:store => :yes},
:role => {},
})
With the above a search that used stop words, ex. "auditor of state", would
return no hits. When I removed the ":index => :untokenized_omit_norms" and
rebuilt the index that same search started to work with acts_as_ferret. I
haven't played around with just using ferret and seeing what would happen
because of time constraints on this current project.
If there's any suggestions or anything I'd gladly try them. I would like to
keep the "desc" untokenized and omit the norms because I don't do boosting
and may wish to sort by the "desc" field.
Thanks,
Curtis
----- Original Message -----
From: "Charlie Hubbard" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, November 07, 2006 9:59 AM
Subject: Re: [Ferret-talk] aaf and stop words; query parser
> Charlie Hubbard wrote:
> > I'm using the same version of AAF and Ferret 0.3.0 and 0.10.9
> > respectively. I sent David Balmain my index so he could analyze it. I
> > posted a similiar message here:
> >
> > http://www.ruby-forum.com/topic/84909
> >
> > Any index I built with AAF seemed to demostrate this problem. I checked
> > the code, but I couldn't see where it might have been modifying the
> > query string in anyway.
> >
> > Any help?
>
> I should also say that I was not able to reproduce this when I created
> an index using just ferret. So doing something similar to what David
> suggested in the other thread. I got hits when I submitted queries with
> stop words. Hope that helps.
>
> Charlie
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Ferret-talk mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/ferret-talk
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
