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
ng Solr?
>
> 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; yo...@lucidimagination.c
magination.com
> Sent: Thu, June 2, 2011 7:00:53 AM
> Subject: query routing with shards
>
> Hello all,
>
> We have currently several pretty fat logically isolated shards with the same
> schema / solrconfig (indices are separate). We currently have one single
> front end
Hello all,
We have currently several pretty fat logically isolated shards with the same
schema / solrconfig (indices are separate). We currently have one single
front end SOLR (1.4) for the client code calls. Since a client code query
usually hits only one shard, we are considering making a smart
