Hibernate 搜索或指南针
我似乎找不到最近关于该选择的任何讨论。早在 06 年，人们就批评 Hibernate Search 不完整并且没有准备好与 Compass 竞争，现在是吗？有没有人同时使用过这两种方法并且对做出决定有一些看法。
我正在空闲时间用 Java 开发一个 Web 应用程序，这只是我自己的事情，所以我希望尽可能地走捷径，同时尽量减少对最终产品的影响。话虽如此，我的项目的搜索能力是第一位的！我花了很多时间制作数据库模型来支持系统。能够为用户提供他们正在寻找的东西将使我的应用程序与众不同。因此，速度是可消耗的……显然在合理的程度上。
以下是我目前对此应用程序技术的想法，如果您发现任何明显的新错误，请保持温和......我什么都不是专家。
数据库：PostgreSQL
平台：Java
框架：Spring、Hibernate、Seam
显然，我选择了所有免费（如啤酒）技术以及据我所知可以很好地协同工作的技术。那么你们觉得用 Compass 还是 Hibernate Search 来解决问题呢？
-Nomad311
I can't seem to find any recent talk on the choice. Back in '06 there was criticism on Hibernate Search as being incomplete and not being ready to compete with Compass, is it now? Has anyone used both and have some perspective on making the decision.
I am developing a web app in Java in my free time, its just me so I'm looking to cut corners everywhere possible while minimizing the effect on the end product. Having said that the searching capabilities of my project are priority one! I have spent a good deal of time making the database model to back the system. The ability to get the user what they're looking for is what will set my app apart. So, speed is expendable ...obviously to a reasonable degree.
Here are my current thoughts on the technologies for this app, and if you see any glaring newb mistakes be gentle ...I'm an expert at nothing.
DB: PostgreSQL
Platform: Java
Frameworks: Spring, Hibernate, Seam
Obviously, I've chosen all free (as in beer) technologies and ones that as far as I can tell play nice together. So what do you guys think, Compass or Hibernate Search to round things out?
-Nomad311
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
<小心。这里有偏见的人：我是 Hibernate Search 的项目负责人，也是 Manning 的 Hibernate Search in Action 的作者>
如果您将 Hibernate 作为持久性提供程序，我认为您最好使用 Hibernate Search，因为集成非常顺利（配置、实体发现使用相同的 API 和编程模型）。
如果您想对数据库中没有的大量“内容”建立索引，那么 Compass 是更合适的选择。
目前我们正在开发 Hibernate Search 3.2：我们的路线图是 此处
<Careful. Biased person here: I am the project lead of Hibernate Search and author of Hibernate Search in Action by Manning>
If you are targeting Hibernate as your persistence provider, I think you are better off using Hibernate Search as the integration is very smooth (configuration, entity discovery down the the same APIs and programamtic model).
If you want to index a lot of "stuffs" that are not in your database, then Compass is a better fit.
We are working on Hibernate Search 3.2 at the moment: our road map is here
Hibernate Search 是一个完整的产品，它基于 Lucene，这是最快的开源搜索引擎之一。
例如，一些基准：
http ://developers.slashdot.org/story/09/07/06/131243/Open-Source-Search-Engine-Benchmarks
另外，它与 Seam 和 Hibernate 完全集成（查看 Seam dist 中的示例） ）。
我建议您更具体地说明：
我想知道哪一部分不完整。
Hibernate Search is a complete product, and it's based on Lucene, which is one of the fastest open source search engine out here.
As an example, some benchmarks:
http://developers.slashdot.org/story/09/07/06/131243/Open-Source-Search-Engine-Benchmarks
Plus, it's fully integrated with Seam and Hibernate (look at the example in the Seam dist).
I suggest you to be more specific about:
I'd like to know in which part it is incomplete.
指南针已不复存在，因为 Elasticsearch 是指南针之后的新搜索引擎。所以我认为最好使用一些稳定的。 （可能是休眠搜索）
Compass is no more as of elasticsearch is new one after compass. So I think better to use some stable one. (Possibly Hibernate Search)