如果你想使用它们,两者一起可能会出现,尽管它需要一些编程工作。 > 这个想法是使用Hibernate Search来完成所有的辛苦工作,然后收集对象的变化并将它们转发给Solr。 这可以通过配置Hibernate Search来完成JMS或通过实现BackendQueueProcessor类并将其注册为hibernate搜索处理器。 如果希望查看一个可用示例,请查看 hibernate_search_solr_integration 。请记住,这只是一个概念演示,您可能需要处理很多问题,例如连接失败,同步问题,线程并发性,软提交优化等等。
For people working with Hibernate to manage their objects persistence, Hibernate search is a real savior. After trying to develop similar functionality (collecting all objects changes and sending them to a full text search engine upon transaction commit) you find out pretty fast that there are lots of pitfalls out there. On the other hand Solr has its own advantages (like 1:m facets for example if you need it) which make it a suitable decision on some scenarios. So if I work with Hibernate as the JPA provider and index my objects on Solr, how can these components be integrated together?
解决方案In case you want to use them both together is turns out it is possible although it will require some programming work. The idea is to work with Hibernate Search to do all the hard work and then collect the objects's changes and forward them to Solr. This can be done either by configuring Hibernate Search to work with JMS or by implementing the BackendQueueProcessor class and registering it as the hibernate search processor. If you wish to check out a working example, check out hibernate_search_solr_integration. Just remember that it's just a concept demonstration and you will probably need to handle lots of issues such as connectivity failure, sync problems, thread concurrency, soft commit optimizations, etc...
更多推荐
如何将Hibernate和Solr集成在一起?
发布评论