nt, which will know what to do with the
>> shards
>> param.
>>
>> Otis
>>
>> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
>> Lucene ecosystem search :: http://search-lucene.com/
>>
>>
>>
>> - Original Message
>&
the
> shards
> param.
>
> Otis
>
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
>
> - Original Message
> > From: Dmitry Kan
> > To: solr-user@lucene.apache.org
> &
osystem search :: http://search-lucene.com/
>
>
>
> - Original Message
> > From: Dmitry Kan
> > To: solr-user@lucene.apache.org
> > Sent: Fri, June 3, 2011 12:56:15 PM
> > Subject: Re: query routing with shards
> >
> > Hi Otis,
> >
&
- Nutch
> > Lucene ecosystem search :: http://search-lucene.com/
> >
> >
> >
> > - Original Message
> > > From: Dmitry Kan
> > > To: solr-user@lucene.apache.org
> > > Sent: Fri, June 3, 2011 2:47:00 AM
> > > Subject:
: solr-user@lucene.apache.org
> > Sent: Fri, June 3, 2011 2:47:00 AM
> > Subject: Re: query routing with shards
> >
> > Hi Otis,
> >
> > I merely followed on the gmail's suggestion to include other people into
> the
> > recipients list, Yonik was t
Subject: Re: query routing with shards
>
> Hi Otis,
>
> I merely followed on the gmail's suggestion to include other people into the
> recipients list, Yonik was the first one :) I won't do it next time.
>
> Thanks for a rapid reply. The reason for doing this query ro
Hi Otis,
I merely followed on the gmail's suggestion to include other people into the
recipients list, Yonik was the first one :) I won't do it next time.
Thanks for a rapid reply. The reason for doing this query routing is that we
abstract the distributed SOLR from the client code for security r
Hi Dmitry (you may not want to additionally copy Yonik, he's subscribed to this
list, too)
It sounds like you have the knowledge of which query maps to which shard. If
so, why not control/change the value of "shards" param in the request to your
front-end Solr (aka distributed request dispatc
