Yes, ferret and acts_as_ferret are notoriously problematic for folk. I've used both solr (with acts_as_solr) and Sphinx (with ultrasphinx) on projects and either seems like a big step up from Ferret.
Rob On Feb 6, 2008 1:22 PM, Chris Petersen <[EMAIL PROTECTED]> wrote: > As I understand it, ferret is "inspired by" Lucene, but not actually based > on the same code. Solr is a separate Java web app that actually uses Lucene. > We've been using Solr, and we've been very happy with it, no stability > problems, and it has been very fast and full featured. However, it is its > own server running on its own ports. For this reason it might be less > appropriate for servers without much memory (VPSs come to mind) or in a > shared hosting environment (I couldn't get it to work on Media Temple at > all). > > Chris > > > > > On Feb 6, 2008 9:47 AM, Adam Grant <[EMAIL PROTECTED]> wrote: > > We have been using Ferret (built on the Lucene indexing engine) with > ActsAsFerret for our company's web sites, and we haven't been very happy > with it. There are currently two big applications deployed that use a > standalone ferret server to index our MySQL database for searching. We get > alot of errors from missing or corrupt index files (10-is a day), and its > getting pretty old. I know some other options are Solr and Sphinx, but it > worries me that Solr is running off of Lucene as well, and I can't say > whether its the ActsAsFerret wapper, the Ruby implementation of that engine, > or the engine itself that is causing our problems. Has anyone run into these > kind of problems with Ferret, and could recommend another, more stable > solution? > > > > Thanks! > > > > - Adam > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
