similar to: Resetting ferret index before test runs

I''m using acts_as_ferret and have indexed a model with acts_as_ferret :fields => [:name, :ascii_name, :alt_names], :single_index => true. Now in the index directory more than 95.000 files are generated! The number of tuples I''m indexing is approx. 86.000. I can''t remember this from earlier ferret/acts_as_ferret versions where I''ve indexed millions of

If I disable ferret in my environment file and then run a cron job every hour to index the records that have been added/changed, do I enable Ferret just in the script that does the hourly indexing? Or do I somehow need to tell the process that runs the Ferret DRB server that it should start writing to the index again? Thanks in advance. Erik

Hi, I''m trying to figure out how to compile ferret with large file support, but none of the topics that discuss this actually say How this is done. Can someone please provide the info? thanks. -m my exact problem: http://www.ruby-forum.com/topic/94143#191630 this topic also discusses the issue: http://www.ruby-forum.com/topic/84237#151791 this topic says that the FAQ should have the

I am experience situations where accessing the index results in a complete re-indexing of the model. I have not been able to detect a pattern. Under what circumstances does Ferret (or AAF) decide that it needs to rebuild the index? I''ll be happy to look at the code relevant to this if someone could direct me to it. Thanks, John

I am looking at trying to use ferret/aaf to supplement my querying against a medium and large table with lots of columns. Some facts first: Ferret 0.11.4 AAF 0.4.0 Ruby 1.8.6 Rails 1.2.3 Medium table: 105,464 rows 168 columns (mostly varchar(20)) 11 actual columns indexed in aaf plus 40 virtual columns indexed in aaf (virtual is concat of two physical columns. e.g. cast_first_name_1 +

Hi all :-) I''m experiencing strange document loss with Ferret 0.11.4 / Ruby 1.8.4. The index handles around 3000 documents, and sometimes during a query_update operation, the delete is done but not the add. That''s very random and happens after a lot of queries (many K). I''ve tried to look into Ferret''s C code, everything looks like going well, the add *LOOKS

Hi all, I cannot make aaf (rev. 220) use my custom analyzer, despite following the indications @ http://projects.jkraemer.net/acts_as_ferret/wiki/AdvancedUsage To pinpoint the problem, I created a model + a simple analyzer with 2 stop words : "fax" and "gsm". test 1 : model.rebuild_index + model.find_by_contents("fax") # fax is a stop word. => I get a

Hi all, I upgraded from Ferret 0.11.3 to Ferret 0.11.4 because I was getting intermittent segfaults that seemed to be due to a bug which was fixed (changeset 749). Unfortunately, 0.11.4 + acts_as_ferret seems to be a bad combination. I''m getting the some "fs_store/File Not Found Error occured at <except.c>:117" which was reported in the "Constant 0.11.4

Hi. We use FerretDrb for search. If the ferret process is down, our entire application comes down the moment we try to save a model which is indexed. Is there a way to decouple this relationship such that we can somehow resume normal operations despite ferret being down and not index the model? Thanks. Morten

Hi, I''ve been having a problem getting highlighting to work with aaf. I have a class defined as follows such: class Link < ActiveRecord::Base acts_as_ferret :fields => { :description => { :store => :yes } } end I get back the correct results when I do Link.find_by_contents, however, I''d like to highlight them. If I do something like iterate through the list of

I''m running Ferret 0.9.5 on a MacBook Pro (OS X 10.4.7) under Locomotive 2.0.7. I have a problem where Ferret is hanging when I try to add items to the index. It doesn''t happen with every object that''s being indexed, and I''m not sure what the objects in question have in common (they are not all instances of the same ActiveRecord object). The process

I''m getting an exception when I query a large index (4GB, ~700K docs) on a particular field. For example: supplier_id:77490 IO Error occured at <except.c>:93 in xraise (IOError) Error occured in fs_store.c:293 - fsi_seek_i seeking pos -1515676213: <Invalid argument> Anecdotally it seems to happen for supplier_ids > 76900. Here is the field info for that

Hi guys, Is there some way of getting ferret matches string, when i do a fuzzy search? The scenario is this: 1. The user search for ''show'' 2. Nothing was found 3. So I do a fuzzy search, passing ''show~'' 4. It gives me somes results, most of all was matched with ''showcase'' 5. So I want to tell the user that: Nothing was found with

Hi All, Hope all is going well. I''m having trouble with the following code creating an in memory index reader - it seems to be attempting to read from a file regardless. Here''s the simple code: require ''rubygems'' require ''ferret'' a = Ferret::Index::Index.new r = Ferret::Index::IndexReader.new(nil) Running the code on my OS X machine

Hi all, I''ve recently started working with Ferret and I''m getting what seems to be slow searches. I have about 10000 documents in the index, with several fields per document, with some fields having an array of several values that are indexed. I am using a RAMDirectory to store the index for searching. When doing testing, I find that searches are reasonable at around .2 to

Hey all! We''ve been using Ferret to great success these past six months. But recently we''ved tried adding many new ContentItems (only thing being index by Ferret at the moment), and things came crashing to a halt. ferret gem: 0.10.9 acts_as_ferret plugin (not sure which version) How we''re using the plugin: class ContentItem < ActiveRecord::Base acts_as_ferret

I''m having a weird problem. Recently, on all my environments, one of my two indexed models is not returning any results to acts_as_ferret. However, the folder is being created for it and Im not receiving any errors. On my two models, I call the following: Book.rebuild_index User.rebuild_index When I call those commands through either my live app "ruby script/server" or

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

Hi ferreters: I''ve already posted this in rails, but someone there suggested this would be better. I''m getting a ferret error when I try to delete any item that has been previously indexed. I just installed ferret, so the indexes aren''t big or anything. What I''m trying to do is to just delete an item on a table that has been index. Here''s the error

AFAICT, ferret_server should be able to handle multiple clients writing to it at once, since ferret itself is thread safe. However, it''s not clear whether running concurrent index rebuilds on different would be possible, since they run inside ferret_server. Anyone have experience with this? -ryan