Yep same thing in rsolr and just use the :shards param. It'll return
whatever solr returns.
Matt
On Wed, Sep 9, 2009 at 4:17 PM, Paul Rosen wrote:
> Hi Erik,
>
> Yes, I've been doing that in my tests, but I also have the case of wanting
> to do a search over all the cores using the shards syntax
The Connection is not for parameters, merely the base URL to the Solr
server (or core, which is effectively a Solr "server").
As of solr-ruby 0.0.6, the shards parameter is supported for the
Solr::Request::Standard and Dismax request objects, so you'd simply
specify :shards=>"" for thos
Hi Erik,
Yes, I've been doing that in my tests, but I also have the case of
wanting to do a search over all the cores using the shards syntax. I was
thinking that the following wouldn't work:
solr =
Solr::Connection.new('http://localhost:8983/solr/core0/select?shards=localhost:8983/solr/cor
With solr-ruby, simply put the core name in the URL of the
Solr::Connection...
solr = Solr::Connection.new('http://localhost:8983/solr/core_name')
Erik
On Sep 9, 2009, at 6:38 PM, Paul Rosen wrote:
Hi all,
I'd like to start experimenting with multicore in a ruby on rails app.
Hi Matt,
What kinds of things were you hoping to find when looking for multicore
support in either solr-ruby or rsolr?
I have a couple of uses for it:
1) Search and merge the results from multiple indexes:
http://localhost:8983/solr/core0/select?shards=localhost:8983/solr/core0,localhost:898
Hey Paul,
In rsolr, you could use the #request method to set a request handler path:
solr.request('/core1/select', :q=>'*:*')
Alternatively, (rsolr and solr-ruby) you could probably handle this by
creating a new instance of a connection object per-core, and then have some
kind of factory to retur
Paul
I've been working with rsolr in a Rails app. In terms of querying from
multiple indices/cores within a multicore setup of Solr, I'm managing it all on
the Rails side, aggregating results from mutliple cores. In terms of core
administration, I've been doing that all by hand as well.
Greg
