Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of calderon.joe@gmail.com
 designates 209.85.217.216 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=Rr/09VF1luRgFgTn6odrjgz2tNzb64gxq5nupIMZtnCQq2R2pbqKn41KsvGeBPSnxb
         3+v9oBNClGxpO1ikSdtG4hE9bfXln21CxsedKawXnDnVUDEg9RnnNd2w2M8AWe407lwY
         JVO5tjz7MlW6GoBVXvNuPmVKqI3SHUPICwo1w=
MIME-Version: 1.0
In-Reply-To: <c68e39171001211145n58a94e95lfdbc658fe5cec26f@mail.gmail.com>
References: <e3cd93651001211139x1dd1133dm3068b16025ee3dbf@mail.gmail.com>
	 <c68e39171001211145n58a94e95lfdbc658fe5cec26f@mail.gmail.com>
Date: Thu, 21 Jan 2010 12:05:05 -0800
Message-ID: <e3cd93651001211205t1c5cbdc7kb4939bb251f2fde8@mail.gmail.com>
Subject: Re: create requesthandler with default shard parameter for different
	query parser
From: Joe Calderon <calderon.joe@gmail.com>
To: solr-user@lucene.apache.org, yonik@lucidimagination.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

thx much, i see now, having request handlers with the same name as the
query parsers was confusing me, i do however have an additional
problem, if i use defType it does indeed use the right query parser
but is there a way to not send all the query parameters in the url
(qf, pf, bf etc), its the main reason im creating the new request
handler, or do i put them all as defaults under my new request handler
and let the query parser use whichever ones it supports?

On Thu, Jan 21, 2010 at 11:45 AM, Yonik Seeley
<yonik@lucidimagination.com> wrote:
> On Thu, Jan 21, 2010 at 2:39 PM, Joe Calderon <calderon.joe@gmail.com> wr=
ote:
>> hello *, what is the best way to create a requesthandler for
>> distributed search with a default shards parameter but that can use
>> different query parsers
>>
>> thus far i have
>>
>> =A0<requestHandler name=3D"/ds" class=3D"solr.SearchHandler">
>> =A0 =A0<!-- default values for query parameters -->
>> =A0 =A0 <lst name=3D"defaults">
>> =A0 =A0 =A0 <str name=3D"fl">*,score</str>
>> =A0 =A0 =A0 <str name=3D"wt">json</str>
>> =A0 =A0 =A0 <str name=3D"shards">host0:8080/solr/core0,host1:8080/solr/c=
ore1,host2:8080/solr/core2,localhost:8080/solr/core3</str>
>> =A0 =A0</lst>
>> =A0 =A0<arr name=3D"components">
>> =A0 =A0 =A0<str>query</str>
>> =A0 =A0 =A0<str>facet</str>
>> =A0 =A0 =A0<str>spellcheck</str>
>> =A0 =A0 =A0<str>debug</str>
>> =A0 =A0</arr>
>> =A0</requestHandler>
>>
>>
>> which works as long as qt=3Dstandard, if i change it to dismax it doenst
>> use the shards parameter anymore...
>
> Legacy terminology causing some confusion I think... qt does stand for
> "query type", but it actually picks the request handler.
> "defType" defines the default query parser to use, so you probably
> don't want to be using "qt" at all.
>
> So try something like:
> http://localhost:8983/solr/ds?defType=3Ddismax&qf=3Dtext&q=3Dfoo
>
> -Yonik
> http://www.lucidimagination.com
>