search for: multitermquery

...e gone beta so the API should be pretty solid now. From now on, backwards compatibility will be a major priority. Also, I''m going to try and do a better job of recording changes and making the release announcements regularly so people know what is going on. == Changes: * Fixed scoring of MultiTermQuery. MultiTermQueries with a high number of terms were being weighted too highly against other queries. * Fixed TUTORIAL so that it is current. On that note, please send in bug reports for documentation errors as well as the usual bug reports. Happy Ferreting Dave

Hi, Apologies for reposting this for those who read this via ruby-forum, but it didn''t make it to the list before, and the list seems more active... I''m using ferret (via acts_as_ferret) in a somewhat unorthodox manner and am having a strange wildcard problem. Before anyone wonders why we''re doing things this way, the answer is basically that it lets us

Hi, I am using acts_as_ferret and have a problem with scoring. I would like to organize it in such way that, if any of the searched terms fits, I get 1.0 score as a result. I will explain it on the example. I have in index: a) "one two three four" b) "one two three" c) "one two" d) "one" When I search for "one" I would like to get 1.0 score for

Hi i''m using ferret to enable geographical postcode. I take a postcode and distance in miles from the user, strip off the outcode and then retrieve the associated x y coordinates in metres from the db. Then i get two temp x''s and y''s and search for all results that are within the box, see code below. Problems start to occur when i search on big distances so for

hey.. i get this error quite regularly, what exactly dies it mean? : Error occured at <q_prefix.c>:54 Error: exception 6 not handled: Too many clauses am i adding to many clauses in the query statement? Ben

How would you go about searching only a specific set of IDs in acts_as_ferret? Should I just create a huge "or" query or is there a more stylish way? Thanks, Winton -- Posted via http://www.ruby-forum.com/.

The included test script turned up the following anomolies (run against Ferret 0.10.3, but had same problems with 0.10.2): 1. When the content word is not in the index the inclusion of a wildcard file term causes search_each to throw a segmentation fault. $ ./test.rb zzz file:*.txt query: +content:zzz +file:*.txt ./test.rb:28: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24)

Hi, I''m confused about managing field boosting ... I have set the :boost for the :name field in my docs to 10, via :boost => 10 Then I performed a search for ''keith'' over all fields via with *:(keith*), expecting a doc with Keith in the :name field to come out on top. But another doc with Keith mentioned in other fields (:comments, :address) scored higher. I

Hi after upgrading to ferret 0.10.1 and bleeding edge aaf i''m getting some strange behavior. Generally much better stability with new version of ferret but when i add new items for some reason i can no longer search with a *. Or rather i can but it returns no results and no errors. I can search and get results normally on other searches and when i rebuild the index i can search with