search for: disable_ferret

Does disable_ferret monkey with callbacks at all? I have a model in my application that has associated models which perform callbacks after their validation (they''re all instantiated around the same time). I recently added a conditional call to disable ferret provided a flag and I''m finding these c...

In my environment.rb I say the following: MyModel.disable_ferret puts MyModel.ferret_enabled? The console works as expected: script/console false >> MyModel.ferret_enabled? => false I can then edit an instance, ferret remains disabled and the changes are not immediately indexed. However, when I start mongrel Ferret is initially disabled, but then...

My index is not being updated when I add new records or amend existing ones. Can anyone point me in the direction of where I should be looking for what is going wrong? I''m running this in the production environment. -- Posted via http://www.ruby-forum.com/.

Hi, I am looking for solution to work with ferret without DRB. I would like to turn off ferret indexing from application and use existing ferret index only for searching (read only), while I would create indexes once a day from script. Is it possible and how to turn indexing off and would ferret still complain if 2 mongrels try to open index file. thanks, Bojan -- Posted via

I have a sellable flag in my database. I''m trying to have ferret only add/update records where sellable == true. What is the best way to do this? I''ve tried editing instance_methods.rb in the AAF, but I still can''t get it to work. Thanks for the help -- Posted via http://www.ruby-forum.com/.

Hi, So i''m trying to use acts_as_taggable with the acts_as_ferret plugin, where I have Post.rb model, which has a method tag_list made available through acts_as_taggable, as returns a string of associated tag words from the tags table (tag.rb). I''ve set up my Post.rb model in the following way. class Post < ActiveRecord::Base acts_as_taggable acts_as_ferret

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 everyone, We''re running a fairly heavily used Rails app that uses ferret (and acts_as_ferret) for search. We''re running on mongrel+Apache, Ruby 1.8.4, and ferret 0.10.13. We''re indexing a handful of attributes on our "Image" and "User" models. After the system has been running for several days, the index gradually becomes corrupted, and ferret

I have seen several threads here and elsewhere about ferret and/or aaf causing seemingly random segfaults in mongrel. However, I didn''t see in any of these threads if a resolution was ever offered. I am currently experiencing this problem and I am keen to get a solution. I appreciate any update that anyone can give me. Best Regards, Danny -- Posted via http://www.ruby-forum.com/.

...non-latin text even in the same room. How can I index both types of strings effectively within the same model field index? 4. Any suggestions on how to build the initial index in an offline way? I suspect it will probably take many hours to build the initial index. 5. I suspect we will have to disable_ferret(:always) on our utterance model, then update the index manually on some periodic basis (cron job, backgroundrb worker, etc.). The reason for this is that we don''t want to introduce any delay into the process of storing a new utterance, which occurs in realtime during a chat session. Anyo...

Everything was working fine till last night. This morning I have many errors. I am using acts_as_ferret. Last updated around a month ago on linux. There are two different type of exceptions. I have over 12 exception emails but these are the two distince types. First exception: A EOFError occurred in home#event_info: End-of-File Error occured at <except.c>:79 in xraise Error occured in

Using the Drb allows me to synchronize writes to the index in a multi mongrel environment. I was under the impression that the remote index would not block if two mongrels were searching the index. Is that the case? This line in ferret_server.rb makes me think otherwise: # Calls are not queued atm, so this will block until the call returned. # def method_missing(name,

hello, I am actually indexing thousands of 1ko text documents using ferret and acts_as_ferret, and i face performance problems. I takes me hours to index 20 000 1ko text documents. Methology used : I create and object, fulfill it with the text, and save it. So it is automaticly indexed. Is there a way to make it faster ? ( remove the auto optimize option somewhere ?) Thank you if you have any

...id with value ''9'' to index Adding field details with value ''test project 9'' to index Adding field notable_type with value ''Project'' to index ....... I also added this to the NotesController: def create @note = Note.new(params[:note]) @note.disable_ferret(:index_when_finished) do @successful = @note.save end ..... end This doesn''t seem to work either, but after I have rebuild the index, the note ''test'' now appears on the results. Did I miss something here? Any help is greatly appreciated. Thanks much, Jackie...

I''d like to be able to enable/disable the automatic indexing of documents acts_as_ferret does. Something like MyModel.disable_indexing MyModel.enable_indexing would be perfect. I need this because I do some indexing that requires visiting the parents of the model objects and my import method imports the children first, so the information isn''t there yet. I''d like to