similar to: is anyone 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

I am using AAF trunk, and I want a way to rebuild an index on a production site with little or no interruption to service. The Drb Server documentation* states that when an index is rebuilt, it is done in a separate location and then swapped into place when finished, and so to do a complete rebuild on a live site, one must take into consideration objects which have been created or

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

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:

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

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

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

Got it all running nicely now for a few days but noticed something funny. I have a table were lots of records get added, deleted every day. I can see the added records being added by AAF to the index but I notices some "ghost" results when doing searches. The search returns record ID-s that do not exist anymore because they were deleted. Does AAF also remove entries from the index when

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

Hi folks. If I am indexing ModelA and ModelB and I want to search both of them, I usually just pick one arbitrarily and use it for #multi_search. Is there a slicker pattern, regarding from which model to invoke #multi_search? Can it be invoked directly from the Ferret library? Has anyone put together some sort of "dummy" search class? Thanks for any ideas. John

Hello. I''m the author of DataMapper (http://datamapper.org), and am trying to choose what Full-Text-Indexing engine/plugin I want to include by default. I was hoping you guys could help. :-) Sphinx comes highly recommended, but without live index updates, it just doesn''t seem practical for most of my work. I''m most experienced with Solr, but the whole HTTP::Request and

Hi, My project has been happily using ActiveRecord outside of Rails for some time to populate various databases that are also used in Rails based websites. I''d like to bring AAF into this setup to index new records that are added to the databases as they''re added. Has anyone had any success in installing and using AAF with ActiveRecord but outside the Rails plugin support? I

I seem to be getting some behaviour thats unexpected (for me anyway) when using find_by_contents on an ActiveRecord has_many association. The results that are returned are only the records that belong to the model returned, but the total_hits that are being returned appear to be for the whole table. e.g. class Book < AR::Base has_many :pages end class Page < AR::Base belongs_to :book

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 =

With AAF I am seeing a strange situation, where a result set has 1 element, but the element is nil, or perhaps sometimes an empty array. I realize this isn''t much to go by, but the rest of my system, and seemingly parallel queries, are working fine. Any suggestions are much appreciated. John

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

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

When trying to start ferret with capistrano, I keep getting this: $ cap services:ferret:stop domain [redken.digitalpulp.com] : user [john] : * executing `services:ferret:stop'' * executing "cd /srv/rails/redken/current; script/ferret_server -e production stop" servers: ["redken.digitalpulp.com"] Password: [redken.digitalpulp.com] executing command ***

I''ve been running some multithreaded tests on Ferret. Using a single Ferret::Index::Index inside a DRb server, it definitely behaves for me as if all readers are locked out of the index when writing is going on in that index, not just optimization -- at least when segment merging happens, which is when the writes take the longest and you can therefore least afford to lock out all reads.

I had sort-by-date working almost perfectly with my app. It was behaving as expected for most data, but had a few hiccups with certain data. I investigated and discovered that the correct data was storing this in my ferret index: "1999-10-18 00:00:00" and the incorrect data was storing this: "Mon Oct 18 00:00:00 EDT 1999" (oops...) So I of course had to fix the