Morten,
If you're still looking at how to solve this, here is what I did.
This is just a hack, but I didn't really have a choice, this coupling
was killing my entire application stack.
--- act_methods.rb (revision 1534)
+++ act_methods.rb (working copy)
@@ -185,9 +185,10 @@
end
logger.info "default field list: #{aaf_configuration[:ferret]
[:default_field].inspect}"
- if options[:remote]
- aaf_index.ensure_index_exists
- end
+ # FIXME fix and send a patch to the AAF team
+ # if options[:remote]
+ # aaf_index.ensure_index_exists
+ # end
end
--
Peter Jones - 303-669-2637
pmade inc. - http://pmade.com
On Nov 11, 2007, at 08:09, Morten wrote:
> 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?
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
