similar to: complete index rebuild using AAF trunk

I''m having problems getting the DRb server running with the aaf gem. I tried it with the plugin installed in my application, and it worked. I suspect the problem has something to do with the startup scripts expecting certain files to be in certain relative file paths. Any insights are appreciated, and maybe if you have time you can update the wiki document :) Thanks for a great

So my ferret behaves nicely in dev mode, but I just deployed and now he is not happy! First thing I noticed was that in general my app would not start with a folder called "development" in my index folder, so I changed it to "production" and now my app is functioning. However, when I try to search I get errors, which you can see here: http://pastie.caboo.se/61767 Im

Hi! Aaf trunk has undergone several major refactorings the last days, with the result that you can now transparently switch your app from local to remote indexing and back :-) If you plan to scale your app to more than one physical machine, or if you have problems with corrupted indexes and the like under high load, you really should give this a try. I wrote some documentation to get you

I blogged about some of the problems with aaf in production (http://www.jroller.com/BrightCandle) yesterday but inspired by the poitive response I thought I would share the perceived problems and discuss some of the potential solutions to help newcomers and make aaf work as if by magic just like Rails does. All of these problems boil down to one simple problem, running acts as ferret in a

Hi all! We use the DRB-Server Backend and are getting strange DRb::DRbConnErrors lately. It started with: too large packet 687865856 (druby:/10.0.0.10:9010) /usr/lib/ruby/1.8/drb/drb.rb:573:in `load'' and later only this one: premature marshal format(can''t read) (druby:/10.0.0.10:9010) /usr/lib/ruby/1.8/drb/drb.rb:580:in `load'' Do you have any ideas what that

I''ve installed the ferret gem. I installed AAF as a plugin into my vendor/plugins directory of my project. In development environment my searches work just fine, without any problems. For production I configured the ferret_server.yml file with correct information about the machine my DRb server is running on. I start the ferret server with the following command: ruby script/runner

hello list! i''m still having massive problems with index rebuilds. after i recently switched to the DRb mode i was hoping to get rid of the problems with locked files and such. but even with DRb and the latest stable version of acts_as_ferret my index rebuilds are failing C:\Informer>ruby script/console production Loading production environment. >> LegacyInfobase.rebuild_index

This is important and may be affecting you if you use :select to minimize the columns you need on big queries. If you use :select to define which columns you need and you have not included all the columns you defined in the :acts_as_ferret field definitions you''ll clear the content of those fields on the ferret index. And that may corrupt your index. So, if you have in your model:

Hi- I''m technical lead at Lingr (http://www.lingr.com), a chatroom-based social networking site. We''ve currently got several million user utterances stored in MySQL, and we''re looking to build a local search functionality. I''ve played around with aaf and I really like it, but I have some questions. 1. Is anyone out there using aaf to index a corpus of this

We all know that using ferret/aaf without the drb server is not thread-safe-- but why not? Would it be so hard to sacrifice performance by using a simple locking system? Very often I run into a situation where I want to quickly stage a project, and I want to use a few mongrels but don''t want to configure every last piece of the system, including the drb server. It would be nice

The documentation states: "single_index: set this to true to let this class use a Ferret index that is shared by all classes having :single_index set to true. :store_class_name is set to true implicitly, as well as index_dir, so don?t bother setting these when using this option. the shared index will be located in index/<RAILS_ENV>/shared ." [1] If I''m reading

We would like to show a list of "most recently added terms", meaning, the results of this query: Resource.aaf_index.ferret_index.reader.terms(:summary) BUT, only returning terms from a certain set of documents (in our case, we are going to filter by creation data). Is this possible? Thanks, John

is the list of indexed words readily available via aaf or directly from ferret? -- Posted via http://www.ruby-forum.com/.

My project is currently using AAF 0.4.3. Trunk has some compelling features, but my project is going live on Monday and I am apprehensive about switching. Is anyone using trunk in a relatively high-volume context? (A low and vague standard for evaluating production suitability, I know, but better than nothing). Thanks, John

The documentation* states that when using a single index for multiple models, the default_field list should be set to the same thing for all models. However, in my application, all my models have very different fields and this is not possible. I still want the results returned sorted by term frequency across all indexed content in each model. What is the purpose of default_field? Under

Hi all, After switching from "regular" AAF to drb based my app is no longer handling nonlatin chars. Any hints? -- Posted via http://www.ruby-forum.com/.

Jesse Grosjean wrote: > I''m trying to write a solaris SMF file to launch the ferret drb server. Hmm, I think I''ve hit a similar problem. I''ve just upgraded to the latest ferret trunk from an old aaf stable where the script/ferret_start and script/ferret_stop scripts were still in use. now if I call the old script... RAILS_ENV=production script/ferret_start

I''m using AAF to search through an AR model, with fields from associated tables included through helper methods in the AR class. The search is working perfectly for the model''s fields, but the data from the associated records aren''t included, it seems. Pastie: http://pastie.caboo.se/93667 I''ve made sure it''s not just a matter of rebuilding the index,

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''m sure I''m missing something completely obvious here, so I hope someone can point me in the right direction! I''ve implemented a basic search with AAF, which works as expected; I''m running a ferret drb server, and using will_paginate to page results. The code in my search_controller.rb: search_text = params[:query] || " " @products =