Elastic Search 与 Sunspot 的功能比较
Couden 找不到任何与 sunspot (Solr) 和 Elastic Search (Lucene) 相关的比较问题 这两个搜索引擎的优缺点是什么？
我看到了其他 VS 问题，以便更好地比较 2 个宝石，因此希望这能让新手（像我一样）更好地了解这两个引擎。我已经研究过太阳黑子，但有一些问题。所以我搜索了
与
Couden't find any compare questions related to sunspot (Solr) to Elastic Search (Lucene)
What would be the pro's and con's on both search engines?
I saw other VS questions to get a better inside in the comparisment of 2 gems so hope this is allowed to get a better insight in the both engines for newbies ( like me ). I have looked at sunspot already but have some issues with it. So I searched
vs
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我开始从事一个需要在 Ruby 中进行全文搜索的项目，所以很自然地我从 Solr + Sunspot 开始，但我无法让它工作。将它们连接起来是一件很痛苦的事情，然后尝试弄清楚文档索引是否正确，找出运行时类路径，以便我可以添加其他分析器/标记生成器类，编辑 config.xml/schema.xml 等。Solr numDocs 清楚说它收到并索引它们，但我无法得到任何查询结果。几天后我就放弃了，这真是一个配置地狱。
ElasticSearch + Tire 的启动和运行非常轻松，我在一小时内就开始工作了。
Lucene 只是一个 Java 搜索库，因此 Solr 被开发为一个完整的服务搜索应用程序，但 Solr 仍然具有典型 Java Web 应用程序的所有陷阱：过于复杂的 XML 配置、模式繁重、需要用于索引的 XML 文档、需要Java servlet 容器（Jetty 或 Tomcat），对我来说已经成为太多的故障点。
ElasticSearch 也基于 Lucene，它有一个内置的 servlet 容器，因此只需像守护进程一样运行，使用非常直接的 JSON + REST API，因此它非常适合测试，并且更自然地适合 Ruby。它是无模式的，它对我来说甚至不需要编辑配置文件就可以工作。一切都很顺利。
我真正需要的是中文搜索，ElasticSearch 已经将 Luecene 的 SmartChineseAnalyzer 打包为插件。如果您需要这种级别的定制，不确定定制分析器/标记器链会有多困难。 ElasticSearch 和 Tire 的文档都是一流的。
Tire（ElasticSearch 的 Ruby 库）
https://github.com/karmi/tire
你可以尝试一下在演示中，它将安装一个rails searchapp，下载ElasticSearch二进制文件并运行它，然后自动启动Webrick。
在我的系统上，它抱怨没有 Javascript 引擎（Rails 3.2？默认不再包含thereubyracer gem），所以我必须：
在文件中添加 gem 'therubyracer' （查找 gem 'tire' 和 gem 'will_paginate'） ，然后...
为了开发我自己的应用程序，我只是下载了 ElasticSearch tarball 并使用 -f 开关在前台运行（这样我可以通过 Ctrl-C 轻松停止它）
您可以安装 eleasticsearch-head 插件来获取 Web 管理界面
https://github.com/mobz/elasticsearch-head
我还发现：如果您有一对多关系模型，Tire 不会在搜索结果中为您解析它们，它只会返回一个平面集合。你的 has_many 和 Belongs_to 关系只是集合中的对象 ID，而不是完整的对象。
I started working on a project that needed full text search in Ruby so naturally I started with Solr + Sunspot, but I couldn't get it to work. It was a pain just the get them connected, then tried to figure out if the document indexed correctly, figure out the runtime classpath so I can add additional analyzer/tokenizer classes, editing config.xml/schema.xml, etc. Solr numDocs clearly said it received and indexed them but I couldn't get any query results. I just gave up after a couple days, it was kind of a configuration hell.
ElasticSearch + Tire was a breezy to get it up and running, I got it working in an hour.
Lucene is just a Java search library, hence Solr was developed to be a full service search app, but Solr still have all the trapping of a typical Java webapp: overly complicated XML configurations, schema-heavy, expect XML docs for indexing, requires a Java servlet container (Jetty or Tomcat), which just become too many points of failure for me.
ElasticSearch is based on Lucene too, it has a built-in servlet container so just run like a daemon, use a very straight forward JSON + REST API so it's great for testing and a more natural fit for Ruby. It's schemaless and it worked for me without even editing a config file. Everything worked beautifully.
What I really needed was Chinese search and ElasticSearch already packaged Luecene's SmartChineseAnalyzer as a plugin. Not sure how difficult it will be to customize the analyzer/tokenizer chain if you need that level of customization. Docmentation for ElasticSearch and Tire are both top-notch.
Tire (Ruby library for ElasticSearch)
https://github.com/karmi/tire
You can try out the demo, it'll install a rails searchapp, download the ElasticSearch binary and run it, then start Webrick automatically.
On my system it complained about not having a Javascript engine (Rails 3.2? no longer include thereubyracer gem by default), so I had to:
add gem 'therubyracer' in the file (look for gem 'tire' and gem 'will_paginate'), then...
For developing my own app, I just downladed the ElasticSearch tarball and run in the foreground with the -f switch (so I can easily stop it by Ctrl-C)
You can install the eleasticsearch-head plugin to get a web admin interface
https://github.com/mobz/elasticsearch-head
Also something I found out: if you have one-to-many relationship models, Tire won't resolve them for you in the search results, it just returns a flat collection. Your has_many and belongs_to relationships will just be object ids in the collection rather than full objects.
我认为你应该搜索 Solr 和 Elastic Search 之间的比较。
事实上sunspot是基于Solr的，而Solr和elasticsearch都是基于Lucene的。它们是两个具有相似目标的不同项目，都构建在 Lucene 之上。
这里有两个比较：
ElasticSearch、Sphinx、Lucene、Solr ，夏皮安。哪个适合哪种用法？
http://www.findbestopensource。 com/article-detail/solr-vs-elasticsearch
I think you should search for a comparison between Solr and elastic search.
In fact sunspot is based on Solr, and both Solr and elastic search are based on Lucene. They are two different projects with similar goals, both built on top of Lucene.
Here are two comparisons:
ElasticSearch, Sphinx, Lucene, Solr, Xapian. Which fits for which usage?
http://www.findbestopensource.com/article-detail/solr-vs-elasticsearch
以下是有关该主题的最完整的最新帖子：http://solr-vs-elasticsearch。 com/
Here is the most complete up-to-date post on the topic: http://solr-vs-elasticsearch.com/