I would tend to agree. -----Original Message----- From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com] Sent: 22 January 2010 05:18 To: solr-user@lucene.apache.org Subject: Re: Solr vs. Compass
Hi Ken, Based on this, Solr sounds like the way to go. Otis -- Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch ----- Original Message ---- > From: Ken Lane (kenlane) <kenl...@cisco.com> > To: solr-user@lucene.apache.org > Sent: Thu, January 21, 2010 12:07:56 PM > Subject: RE: Solr vs. Compass > > Uri, Lucas, > > Thanks for your feedback. To clarify on some specifics, > > 1. Yes, faceted search and DisMax are very imortant to this project. > 2. Our data is imported from Oracle tables. (Unstructured sources maybe > later). > We manufacture each document from DB queries. > 3. Our platform won't be transactional, we will update the indexes > periodically throughout the day probably via dataimport handler. > > Regards, Ken > > -----Original Message----- > From: Uri Boness [mailto:ubon...@gmail.com] > Sent: Thursday, January 21, 2010 11:35 AM > To: solr-user@lucene.apache.org > Subject: Re: Solr vs. Compass > > In addition, the biggest appealing feature in Compass is that it's > transactional and therefore integrates well with your infrastructure > (Spring/EJB, Hibernate, JPA, etc...). This obviously is nice for some > systems (not very large scale ones) and the programming model is clean. > On the other hand, Solr scales much better and provides a load of > functionality that otherwise you'll have to custom build on top of > Compass/Lucene. > > Lukáš Vlček wrote: > > Hi, > > > > I think that these products do not compete directly that much, each > > fit different business case. Can you tell us more about our specific > > situation? > > What do you need to search and where your data is? (DB, Filesystem, > > Web > > ...?) > > > > Solr provides some specific extensions which are not supported > > directly by Lucene (faceted search, DisMax... etc) so if you need > > these then your bet on Compass might not be perfect. On the other > > hand if you need to index persistent Java objects then Compass fits > > perfectly into this scenario (and if you are using Spring and JPA > > then setting up search can be matter of several modifications to > > configuration and annotations). > > > > Compass is more Hibernate search competitor (but Compass is not > > limited to Hibernate only and is not even limited to DB content as well). > > > > Regards, > > Lukas > > > > > > On Thu, Jan 21, 2010 at 4:40 PM, Ken Lane (kenlane) wrote: > > > > > >> We are knee-deep in a Solr project to provide a web services layer > >> between our Oracle DB's and a web front end to be named later to > >> supplement our numerous Business Intelligence dashboards. Someone > >> from a peer group questioned why we selected Solr rather than > >> Compass to start development. The real reason is that we had not > >> heard of Compass until that comment. Now I need to come up with a better > >> answer. > >> > >> > >> > >> Does anyone out there have experience in both approaches who might > >> be able to give a quick compare and contrast? > >> > >> > >> > >> Thanks in advance, > >> > >> Ken > >> > >> > >> > > > > =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================
