similar to: Two repeatable crash bugs in Ferret proper

I have found another crash in ferret; this one just uses a regular search. It''s similar to an issue reported by Matt Schnitz a while ago, but unlike his, mine does not go away if I turn off omit_norms. It does go away if I turn on the garbage collector more often, but I''m not sure that''s a stable workaround under the circumstances. This one isn''t a

I''m running: ferret (0.10.9) ruby 1.8.5 (2006-08-25) [i386-mswin32] on Windows XP(SP2) When I create an index as follows: field_infos = FieldInfos.new(:store => :yes, :term_vector => :no, :index => :yes) field_infos.add_field(:id, :index => :untokenized) field_infos.add_field(:subject) field_infos.add_field(:author) field_infos.add_field(:tags, :store => :no) index =

Hey Dave, I just contributed $100 to the ferret donation box. My project is earning no money yet (but hopefully will), for now I hope this helps you out and covers me for asking stupid questions ;). To get a distance sorted output, I am passing an array of the id field from a ferret search through to mysql in a custom select statement. SELECT ... id IN (#{ids.join(",")}) This has

I have a lot of crashes when I try to use term vectors. Here''s an example, which crashes pretty consistently. This problem seems to be somewhat sensitive to platform... people on other OS''s and ruby versions have reported no error. I have seen this with ferret 0.10.13 and 0.10.14 on debian stable using ruby 1.8.2, but I have observed the same problem on various other systems as

The following script creates a search index and then searches it. I get no results? Where am I going wrong? Thanks. -----------BEGIN SCRIPT---------------- require ''rubygems'' require ''ferret'' include Ferret path = ''/tmp/myindex'' field_infos = Ferret::Index::FieldInfos.new() field_infos.add_field(:name, :store => :yes, :index => :yes)

Hi, Using the 0.10.4 gem under ruby 1.8.5 (2006-08-25) [i686-linux], I get different results with a TermQuery and a search string. Namely, using a search string seems to always work whereas using a TermQuery often doesn''t return any entries. For example: > x=@i[450][:message_id] => "9e7db9110509070759732b21c4 at mail.gmail.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)

Hello, What''s the best way to handle formating of a text_area? I have a text_area in my rails app where people can leave comments and I''d like to automatically convert the line breaks into <br /> tags, or just simply wrap a whole paragraph in <p></p> tags. I''m currently doing the following in my comments controller to insert line breaks when the user

Hi .. I tried to exclude certain objects from my search, by adding appropriate term queries .. i = Ferret::Index::Index.new i.field_infos.add_field(:type, :index => :untokenized, :term_vector => :no) i << {:type => "Movie", :name => "Indiana" } i << {:type => "Movie", :name => "Forrest" } i << {:type =>

Hi, I''m trying out the example (more or less) straight from the tutorial: doc = Document.new doc << Field.new("id", "a", Field::Store::NO, Field::Index::UNTOKENIZED) doc << Field.new("title", "b", Field::Store::YES, Field::Index::UNTOKENIZED) doc << Field.new("data", "c",

Hi there, Is highlighting for range queries supposed to work ? It doesn''t work here. here is an non-working example: (highlighting works when q="test:2007*") require ''ferret'' include Ferret index = Index::Index.new() #index.field_infos.add_field(:test, :store => :yes, :index => :untokenized) i=1 for a in [ "20070505", "20071230",

Dave, thank you so much for the 0.11 release(s). You have solved many problems for me. As part of my appreciation for your good works, I am offering up for public consideration a silly little class that I wrote. (Code is below.) This class offers a simplified Hash-like interface to (a very restricted subset of) Ferret. Hence I call it FerretHash. FerretHash comes with its very own pet Ferret

I''ve been messing around with Ferret (no punn intended). After spending some time testing it out (indexing to file), I decided to index about 10% of the data I want to eventually index. It took several hours to complete the index on my local machine, but it was created without any problems and after optimising it the searches returned results at the sort of speed I was expecting. I

My linux Ruby application is using Ferret 0.11.4. I created my own class IndexSearcher to contain the Searcher of multiple directories. If I do not have the searcher.close called, the end of runner/console or runner/server will pop out with system error: *** glibc detected *** irb: double free or corruption (fasttop): 0x0a51d6c0 *** ======= Backtrace: ========= /lib/libc.so.6[0x638ac1]

I was under the impression that Model.rebuild_index will automatically call optimize in the end. But that doesn''t seem to be the case. After running Model.rebuild_index how do I optimize the index. I am using aaf most stable and also ferret most stable. def rebuild_index(*models) models << aaf_configuration[:class_name] unless

hi, i''m indexing a really large db table (~4.2 million rows). i''ve noticed that after ~2M records, index performance decreases by almost an order of magnitude. full dataset graph here: http://i122.photobucket.com/albums/o244/spokeo/indexer-data.jpg here''s a couple best-fit lines that represent the data points: 0-2M : y = 78.65655x + 144237.5 2.5M+ : y = 10.79832x +

Hi, I''m adding some news articles to a keyed Ferret 0.10.14 index and encountering quite serious instability when concurrently reading and writing to the index, even though with just 1 writer and 1 reader process. If I recreate the index without a key, concurrent reading and writing seem to work fine (and indexing is about 10 times quicker :) I''m testing by running my indexing

Thanks Stuart. I thought I had read somewhere that rebuild_index built the index in a different location and then swapped it, but after looking at the code (in local_index.rb) this doesn''t appear to be the case. That might explain why the ferret server crashes sometimes when a search takes place during a reindex. I wouldn''t be doing exactly the same thing as this but

I have a script (below) which attempts to make an index out of all the man pages on my system. It takes a while, mostly because it runs man over and over... but anyway, as time goes on the memory usage goes up and up and never down. Eventually, it runs out of ram and just starts thrashing up the swap space, pretty much grinding to a halt. The workaround would seem to be to index documents in

Hi, Just downloaded the new ferret 0.11. I''m on OSX btw. I get this error everytime I run my unit tests: Loaded suite ferret_updater_unit_test Started E/usr/local/lib/ruby/1.8/erb.rb:504: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i686-darwin8.7.1] Abort trap When I revert back to 10.14 I dont get this error. When I comment out the line: Ferret::Index::Index.new({:path =>