On Fri, 2008-09-12 at 16:44 -0400, Yonik Seeley wrote:
> On Fri, Sep 12, 2008 at 9:02 AM, Upayavira <[EMAIL PROTECTED]> wrote:
> > On Fri, 2008-09-12 at 06:05 -0400, Erik Hatcher wrote:
> >> Is your interest in moving the shards parameter to the
> >> server-side instead? You can do that with the
On Fri, 2008-09-12 at 14:02 +0100, Upayavira wrote:
> On Fri, 2008-09-12 at 06:05 -0400, Erik Hatcher wrote:
> > Even in the example in that page, the client _is_ just querying a
> > single Solr instance - it is that Solr instance that is then querying
> > the shards. Is your interest in movin
On Fri, Sep 12, 2008 at 9:02 AM, Upayavira <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-09-12 at 06:05 -0400, Erik Hatcher wrote:
>> Is your interest in moving the shards parameter to the
>> server-side instead? You can do that with the request handler
>> mapping configuration in solrconfig.xml, and
On Fri, 2008-09-12 at 06:05 -0400, Erik Hatcher wrote:
> Even in the example in that page, the client _is_ just querying a
> single Solr instance - it is that Solr instance that is then querying
> the shards. Is your interest in moving the shards parameter to the
> server-side instead? You
Even in the example in that page, the client _is_ just querying a
single Solr instance - it is that Solr instance that is then querying
the shards. Is your interest in moving the shards parameter to the
server-side instead? You can do that with the request handler
mapping configuration i
> Does anything like this exist, or do I have to write it?
It doesn't come with Solr, but it should be quite easy to implement a proxy e.g.
with Apache httpd mod_rewrite [1].
Lars
[1] http://httpd.apache.org/docs/2.2/rewrite/
The http://wiki.apache.org/solr/DistributedSearch page implies that you
must know what shards exist when doing a search across multiple shards.
A colleague tells me that there is a feature that makes it possible to
hide this knowledge.
That is, a something that you query that then forwards your q
