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) <kenl...@cisco.com>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 > >
