Thanks Ian for sharing your knowledge on this.
We've been going through the recently published "Solr 1.4 Enterprise Search
Server" book and came across some stuff that means - Acts_as_Solr schema
could be less flexible when it comes to complex indexing and faceting of the
fields.
We are still exp
Hi,
Thanks for the discussion. We use the distributed option so I am not sure
embedded is possible.
As you also guessed, we use haproxy for load balancing and failover between
replicas of the shards so giving this up for a minor performance boost is
probably not wise.
So essentially we have: Use
On Sep 18, 2009, at 1:09 AM, rajan chandi wrote:
We are planning to use the external Solr on tomcat for scalability
reasons.
We thought that EmbeddedSolrServer uses HTTP too to talk with Ruby and
vise-versa as in acts_as_solr ruby plugin.
EmbeddedSolrServer is a way to run Solr as an API (l
We are planning to use the external Solr on tomcat for scalability reasons.
We thought that EmbeddedSolrServer uses HTTP too to talk with Ruby and
vise-versa as in acts_as_solr ruby plugin.
If Ruby is not using the HTTP to talk EmbeddedSolrServer, what is it using?
Thanks and Regards
Rajan Chand
On Sep 17, 2009, at 11:40 AM, Ian Connor wrote:
Is there any support for connection pooling or a more optimized data
exchange format?
The solr-ruby library (as do other Solr + Ruby libraries) use the ruby
response format and eval it. solr-ruby supports keeping the HTTP
connection alive to
Hi,
Is there any support for connection pooling or a more optimized data
exchange format? We are looking at any further ways to optimize the solr
queries so we can possibly make more of them in the one request.
The JSON like format seems pretty tight but I understand when the
distributed search t
