Re: [hibernate-dev] Using SOLR with indexing/search Server
Hi Hardy
HIbernate provide what i need to search/indexing. But In SOLR scalability
feature is more transparent and i dont have to implements JMS Queue or
something to synchronized master with slaves. Also, solr provides multicore
feature, where i can put many index in one instance of SOLR.
Our team decided to use SOLR. We just wanted to use HIbernate like a
developer API and SOLR as server for index/search. Since this is not
possible, we will use SOLRJ API and who Knows we increments this API.
Thanks a lot for your help and considerations
Regards
Anderson
2012/1/26 Hardy Ferentschik <hardy(a)hibernate.org>
On Jan 26, 2012, at 3:01 AM, Anderson vasconcelos wrote:
> Hi Hardy, Thanks for the reply.
> I Wanna use HIbernate Search, because it has a lot of features that
SOLRJ doesn't have, like embebed objects mapping, easy way to call search
(because is similar to create HQL query) and easy way to integrate database
data with index data.
> For developers, Hibernate Search is more easy to use.
That's good to hear :-)
> Also, i wanna use solr like a search server ( with master, slaves and
shards).
Hibernate Search also offers master/slave setups using JMS or JGroups for
communication between master and slaves. Have a look at
http://docs.jboss.org/hibernate/stable/search/reference/en-US/html_single...
Also it is possible to split large indexes into multiple shards (if this
is what you mean with sharding). Do you have a concrete use case or
requirement you think Search cannot meet?
--Hardy