blocks|key|3371142|text|Thinking有更简洁的语法来定义哪些字段和哪些模型被索引。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3371143|UltraSphinx和which+(最近)都有超酷的特性，它考虑到了物体的地理位置接近。|3371144|UltraSphinx在加载模型的方式上有一些恼人的问题(它不加载整个Rails堆栈，所以您可能会感到奇怪，很难诊断错误，这些错误是通过添加显式的require语句来处理的)。|offset|length|style|CODE|3371145|我们在新项目上使用Thinking，在使用地理内容的项目上使用UltraSphinx。|3371146|entityMap^0|0|0|21|7|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Thinking Sphinx has more concise syntax to define which fields and which models are indexed.

Both UltraSphinx and Thinking Sphinx (recently) have ultra-cool feature which takes into account geographical proximity of objects. 

UltraSphinx has annoying problems with how it loads models (it does not load entire Rails stack, so you could get strange and hard to diagnose errors, which are handled by adding explicit <code>require</code> statements).

We use Thinking Sphinx on new projects, and UltraSphinx on projects which use geo content.

blocks|key|365173|text|这个问题之前已经在here上被问过，并有更详细的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|365174|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/47656/how-do-i-do-full-text-searching-in-ruby-on-rails^0|9|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This question has been asked previously <a href="https://stackoverflow.com/questions/47656/how-do-i-do-full-text-searching-in-ruby-on-rails">here</a> with more detailed answers.

blocks|key|3371192|text|我的一个朋友使用的一个可靠的选择是Solr，这是一个使用原始的基于Java的Lucene的搜索引擎。要在Rails中使用它，当然还有一个acts_as插件acts_as_solr。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3371193|他最近在Montreal+on+Rails上展示了这个组合，并对how+to+use+acts_as_solr+on+his+blog进行了很好和全面的概述。|3371194|它显然也很好地支持法国口音。|3371195|entityMap|0|LINK|mutability|MUTABLE|url|http://lucene.apache.org/solr/|1|http://github.com/railsfreaks/acts_as_solr/tree/master|2|http://www.montrealonrails.com/2008/08/20/10-was-a-success/|3|http://hugofrappier.wordpress.com/2008/09/01/solr-presentation-at-montreal-on-rails/^0|H|4|0|25|C|1|0|4|H|2|W|Z|3|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]|$A|16|B|17|1|18]]|C|$]]|$1|F|3|G|5|6|7|19|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]|T|$5|K|L|M|C|$N|U]]]]

A solid option used by one of my friends is <a href="http://lucene.apache.org/solr/" rel="noreferrer">Solr</a>, a search engine using the original Java-based Lucene. To use it with Rails, there's, of course an acts_as plugin, <a href="http://github.com/railsfreaks/acts_as_solr/tree/master" rel="noreferrer">acts_as_solr</a>.

He presented the combo recently at <a href="http://www.montrealonrails.com/2008/08/20/10-was-a-success/" rel="noreferrer">Montreal on Rails</a> and gives a nice and thorough overview of <a href="http://hugofrappier.wordpress.com/2008/09/01/solr-presentation-at-montreal-on-rails/" rel="noreferrer">how to use acts_as_solr on his blog</a>.

It apparently supports french accents very well, too.

blocks|key|3158531|text|我现在正在经历这个过程，所以虽然我没有实际的经验，但我花了很多时间研究所有的选择。这是我到目前为止所学到的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3158532|3158533|*Sphinx+-速度和功能方面的好名声，但Sphinx需要整数键，而我的模型使用GUID；ThinkingSphinx最近宣布支持GeoSpatial+|unordered-list-item|3158534|Acts_As_Solr+-由一个高容量站点的朋友推荐；原始创建者已经停止开发它，文档很难找到；需要Java+servlet|3158535|Acts_As_Ferret+-看起来很容易使用，但许多批评者说它的|3158536|不稳定另外两个信息有限的是Acts_As_Indexed和GUID|3158537|3158538|我有一个电子表格，试图记录所有这些方法的优缺点。如果任何人有兴趣查看和/或帮助我更正它，请与我联系。一旦我知道它是准确的，我会把它贴到某个地方。|3158539|我的建议是，如果您有普通的主键，可以尝试使用UltraSphinx或Thinking。根据良好的文档、功能集以及项目的活跃程度，我将尝试使用Acts_As_Xapian。|3158540|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|X|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

I'm going through this exact process right now so while I don't have actual experience, I've spent many hours researching all the options. Here's what I've learned so far:

<ul>
<li>*Sphinx - good reputation for speed and functionality but Sphinx needs integer keys and my model uses GUID; ThinkingSphinx recently announced support for GeoSpatial </li>
<li>Acts_As_Solr - recommended by a friend with a high-volume site; original creators have stopped working on it and documentation is hard to find; requires a Java servlet</li>
<li>Acts_As_Ferret - looks easy to use, but lots of detractors that say its unstable</li>
<li>Two others with limited information are Acts_As_Indexed and Acts_As_Searchable</li>
</ul>

I have a spreadsheet with my attempt at documenting the advantages and disadvantages of all of them. If anyone is interested in seeing it and/or helping me correct it, just contact me. I'll post it somewhere once I know its accurate.

My recommendation would be to try UltraSphinx or Thinking Sphinx if you have normal primary keys. I'm going to try Acts_As_Xapian based on the good documentation, feature set, and how active the project seems to be.

blocks|key|3371160|text|我只在一个客户项目上使用了Ferret/acts_as_ferret组合(遗留决策)。我强烈建议先看看other选项。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3371161|aaf非常脆弱，如果你在配置中犯了错误，或者由于某种原因，你在aaf中遇到了错误，aaf可能会让你的Rails应用程序突然停止。|3371162|在这种情况下，不是简单地让搜索功能失效，而是任何涉及索引模型的控制器操作都将完全失败并引发异常。哪一个是巴德，嗯？|3371163|entityMap^0|1F|5|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

I have only used the Ferret/acts_as_ferret combo (legacy decision) on a client project. I strongly recommend looking at the other options first.

aaf is very fragile and can bring your Rails app to a screeching halt if you make a mistake in the config or if for some reason you hit a bug in aaf. 

In such a case, instead of simply having the search functionality crapping out, any controller action touching an indexed model will completely fail and raise an exception. Which is baaad, hmkay?

blocks|key|368197|text|我使用acts_as_xapian插件。我遵循了以下教程：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|368198|http://locomotivation.com/2008/07/23/simple-ruby-on-rails-full-text-search-using-xapian|offset|length|368199|效果非常好。|368200|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2F|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

I use the acts_as_xapian plugin. I followed this tutorial: 

<a href="http://locomotivation.com/2008/07/23/simple-ruby-on-rails-full-text-search-using-xapian" rel="nofollow noreferrer">http://locomotivation.com/2008/07/23/simple-ruby-on-rails-full-text-search-using-xapian</a>

Works very well.

blocks|key|368285|text|我使用的是acts_as_ferret。它很容易配置，而且通常速度很快。内置的活动记录查找功能非常有用:在搜索找到匹配的记录后，您可以应用任何条件或加入其他模型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|368286|与sphinx不同的是，当您添加新数据时，不必重新索引所有记录。有after_save和after_update钩子可以将您的新记录插入到ferret数据库中。这是我最大的卖点之一。|368287|当您确实需要对数据进行海量索引时，ferret绝对比acts_as_sphinx慢(慢3倍)。我最终编写了自己的方法来重新索引模型，它的速度与sphinx一样快--它基本上是从DB预加载所有数据，而不是逐条记录地创建新的索引。|368288|ferret文档对基础知识很有帮助，但是一旦涉及到更复杂的搜索、排序和使用dRb服务器托管远程索引，它就有点稀疏了。话虽如此，但我觉得它比acts_as_sphinx成熟得多，尽管我对sphinx的使用经验有限。|368289|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I'm using acts_as_ferret. It's easy to configure and generally fast. The built-in active record find functionality is quite useful: you can apply any conditions or join other models after your search finds the matching records. 

Unlike sphinx, you don't have to re-index ALL of your records when you add new data. There are after_save and after_update hooks that will insert your new record into the ferret db. This was one of the big selling points for me.

When you do have to mass index your data, ferret is definitely slower than acts_as_sphinx (by a factor of 3). I ended up writing my own method to re-index models which works as fast as sphinx -- it basically preloads all the data from the DB instead of going record by record to create the new index.

The ferret documentation is good for the basics, but it's a bit sparse once you get into more complex searches, sorts and using a dRb server to host a remote index. That being said, it feels a much more mature product than acts_as_sphinx, although I have limited experience with sphinx.

blocks|key|3371444|text|如果您使用的是像我这样的共享主机服务(Bluehost)，您的选择可能会受到提供商提供的服务的限制。在我的例子中，我找不到一种好的、可靠的方法来启动和保持单独的服务器运行，比如Lucene或Solr。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3371445|因此，我选择了Xapian，它对我来说运行得很好。我研究过两个rails插件:+acts_as_xapian和xapian_fu。第一个可以让你快速前进，但它似乎不再需要维护。我刚刚开始使用xapian_fu。|3371446|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you are using a shared hosting service like me (Bluehost), your options may be limited to what the provider offers. In my case, I couldn't find a good and reliable way to start and keep a separate server running, such as Lucene or Solr.

Therefore, I went with Xapian and it's been working well for me. There are 2 plugins for rails I've researched: acts_as_xapian and xapian_fu.
The first will get you going quickly, but it doesn't seem to be maintained anymore. I've just begun working with xapian_fu.

blocks|key|3371562|text|如果还有人对此感兴趣，现在最新使用的是elasticsearch.有像轮胎或elasticsearch-rails.这样的宝石可供选择它也是基于Lucene的，比如Solr，基于Java。Solr现在实际上已经与这个项目集成在一起了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3371563|entityMap^0|J|D|Z|2|12|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

In case anyone is still interested, the latest thing to use now is elasticsearch. There are gems available for it like tire or elasticsearch-rails. It is also based on Lucene like Solr, Java-based. Solr is actually integrated with this project now...

blocks|key|3371101|text|我使用过time，它看起来很不错，但我还没有时间来评估所有的选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3371102|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've used Thinking Sphinx and it seems pretty good, but I haven't had the time to evaluate all of the options.

blocks|key|3158382|text|我建议您考虑使用Sphinx。在我看来，这是最快的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3158383|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I recommend Thinking Sphinx. It is the fastest option in my opinion.

blocks|key|364724|text|我已经使用了Ferret，它在我的目的上工作得很好，但我还没有评估其他的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364725|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've used Ferret and it worked well for my purposes, but I have not evaluated the other options.

blocks|key|368194|text|我还没有尝试过的一个选择是基于C%2B%2B的Xapian|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|368195|entityMap|0|LINK|mutability|MUTABLE|url|http://www.xapian.org/^0|J|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

An option I haven't tried is the C++ based <a href="http://www.xapian.org/" rel="nofollow noreferrer">Xapian</a>

blocks|key|363365|text|我们使用的是继承的http://hyperestraier.sourceforge.net/。我没有研究过其他引擎，但hyperestraier提供了所有必要的钩子。不过，设置搜索索引很复杂。可能会有更简单的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|363366|entityMap|0|LINK|mutability|MUTABLE|url|http://hyperestraier.sourceforge.net/^0|9|11|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

We're using <a href="http://hyperestraier.sourceforge.net/" rel="nofollow noreferrer">http://hyperestraier.sourceforge.net/</a>, which was inherited. Haven't looked into other engines, but hyperestraier provides all the hooks necessary. Setting up the search index is complicated though. Probably easier options available.

blocks|key|364871|text|这取决于您使用的数据库。我推荐使用Solr，因为它为模糊搜索提供了很多很好的选项，并且有一个很棒的查询解析器。缺点是你必须为它运行一个单独的进程。我也使用过Ferret，但发现它在多线程访问索引方面不太稳定。我还没有尝试过Sphinx，因为它只适用于MySQL和Postgres。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364872|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It depends on what database you are using. I would recommend using Solr as it offers up a lot of nice options for fuzzy search and has a great query parser. The downside is you have to run a separate process for it. I have used Ferret as well, but found it to be less stable in terms of multi-threaded access to the index. I haven't tried Sphinx because it only works with MySQL and Postgres.

blocks|key|364882|text|我使用了一个不同的选项，这个选项运行得非常好。我正在使用jruby并直接与lucene对话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364883|我过去使用过acts_as_solr，遇到了一些问题。它主要为每个AR存储发出一个同步调用。这并不是太糟糕，但在我的情况下，保存有时会导致对solr的许多同步调用，并且偶尔会花费比mongrel所允许的更长的时间，并且我会得到一个mongrel超时异常(或者类似的异常)。|364884|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'm using a different option which was worked out amazingly well. I'm using jruby and talking to lucene directly. 

I've used acts_as_solr in the past and ran into some issues. mainly it makes a synchronous call for each AR save. This isn't too bad, but in my situation a save sometimes caused many synchronous calls to solr and would occasionally take longer than mongrel would allow and I'd get a mongrel timeout exception (or something like that)

blocks|key|3158653|text|认为Sphinx是一个比Ultrasphinx更好的选择，后者似乎被抛弃了，但总的来说，Xapian拥有比Sphinx更强大的引擎，更容易实现实时搜索。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3158654|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Thinking Sphinx is a better alternative than Ultrasphinx, which seems abandoned, but, in general, Xapian has a more powerful engine than Sphinx and is easier for implementing realtime search.

blocks|key|365234|text|我推荐acts_as_ferret。但是，尽管困难的部分是让它在您的服务器上成功启动和运行，一旦完成，您几乎没有任何问题，因为ferret服务器将作为单独的后台进程运行，以在每次有任何新的更新时更新您的索引。此外，它在apache和我们的混合中工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|365235|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I recommend acts_as_ferret. But though the tough part is to get it up and running successfully in your server, once done you hardly have any problem as ferret server will be running as separate background process to update your index every time there is any new update. Also, its working great in mongrel with apache for us.

blocks|key|3158681|text|我也一直在寻找完美的解决方案。一开始，我选择了Sphinx，它工作得很好。但由于我打算在Heroku上托管我的webapp，所以唯一的选择就是使用Solr。然而，最大的缺点是，主要的acts_as_solr创业板的开发似乎在2008年5月之后就停止了。所以这对我来说太老了。我刚刚发现Sunspot是一个高级的替代方案，并且最近有更新，所以这是我要考虑的一个。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3158682|Heroku提供的另一个选择是基于Solr的托管索引服务器，名为Websolr。幸运的是，所需的gem+websolr-acts_as_solr也是最新的。|3158683|entityMap|0|LINK|mutability|MUTABLE|url|http://www.heroku.com/|1|http://lucene.apache.org/solr/|2|http://github.com/railsfreaks/acts_as_solr|3|http://outoftime.github.com/sunspot/|4|http://www.websolr.com/|5|http://github.com/onemorecloud/websolr-acts_as_solr^0|18|6|0|21|4|1|2J|C|2|3Y|7|3|0|W|7|4|1G|K|5|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]|$A|11|B|12|1|13]|$A|14|B|15|1|16]|$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]|$A|1E|B|1F|1|1G]]|C|$]]|$1|F|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]|R|$5|I|J|K|C|$L|S]]|T|$5|I|J|K|C|$L|U]]|V|$5|I|J|K|C|$L|W]]]]

I've been looking for the perfect solution as well. At first I went with Thinking Sphinx, which worked fine. But since I intent to host my webapp on <a href="http://www.heroku.com" rel="nofollow noreferrer">Heroku</a>, the only option is to use <a href="http://lucene.apache.org/solr/" rel="nofollow noreferrer">Solr</a>. The biggest drawback, however, is that development of the main <a href="http://github.com/railsfreaks/acts_as_solr" rel="nofollow noreferrer">acts_as_solr</a> gem seems to have stopped after May 2008. So that's too old for my taste. I just found <a href="http://outoftime.github.com/sunspot/" rel="nofollow noreferrer">Sunspot</a> as an advanced alternative and with recent updates, so that's one I'm going to consider.

Another option Heroku offers is to go for a hosted index server based on Solr, named <a href="http://www.websolr.com/" rel="nofollow noreferrer">Websolr</a>. The required gem <a href="http://github.com/onemorecloud/websolr-acts_as_solr" rel="nofollow noreferrer">websolr-acts_as_solr</a> is also luckily very much up-to-date.

There are several plugin options for building a search engine into your Ruby on Rails application. Which of these is the best?

<ul>
<li><a href="http://ts.freelancing-gods.com/" rel="noreferrer">Thinking Sphinx</a></li>
<li><a href="http://blog.evanweaver.com/files/doc/fauna/ultrasphinx/files/README.html" rel="noreferrer">UltraSphinx</a></li>
<li><a href="http://seattlerb.rubyforge.org/Sphincter/" rel="noreferrer">Sphincter</a></li>
<li><a href="http://www.datanoise.com/articles/2007/3/23/acts_as_sphinx-plugin" rel="noreferrer">acts_as_sphinx</a></li>
<li><a href="http://projects.jkraemer.net/acts_as_ferret/" rel="noreferrer">acts_as_ferret</a></li>
<li><a href="http://ferret.davebalmain.com/trac/" rel="noreferrer">Ferret</a></li>
<li><a href="http://locomotivation.com/2008/07/23/simple-ruby-on-rails-full-text-search-using-xapian" rel="noreferrer">acts_as_xapian</a></li>
<li><a href="http://github.com/railsfreaks/acts_as_solr/tree/master" rel="noreferrer">acts_as_solr</a></li>
<li><a href="http://hyperestraier.sourceforge.net/" rel="noreferrer">Hyper Estraier</a></li>
</ul>

What's the best option for searching in Ruby on Rails?

Elasticsearch 

数据库

服务器

MySQL

Java

有几个插件选项可以将搜索引擎构建到Ruby on Rails应用程序中。哪一个是最好的？

问在Ruby on Rails中搜索的最佳选择是什么？
EN

回答 19

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Ruby on Rails中搜索的最佳选择是什么？EN

回答 19

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Ruby on Rails中搜索的最佳选择是什么？
EN