Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6ECDD91AB for ; Fri, 24 Feb 2012 19:06:55 +0000 (UTC) Received: (qmail 1595 invoked by uid 500); 24 Feb 2012 19:06:54 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 1538 invoked by uid 500); 24 Feb 2012 19:06:54 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 1531 invoked by uid 99); 24 Feb 2012 19:06:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2012 19:06:54 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ryantxu@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-tul01m020-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2012 19:06:49 +0000 Received: by obbwd18 with SMTP id wd18so4671455obb.35 for ; Fri, 24 Feb 2012 11:06:28 -0800 (PST) Received-SPF: pass (google.com: domain of ryantxu@gmail.com designates 10.182.76.229 as permitted sender) client-ip=10.182.76.229; Authentication-Results: mr.google.com; spf=pass (google.com: domain of ryantxu@gmail.com designates 10.182.76.229 as permitted sender) smtp.mail=ryantxu@gmail.com; dkim=pass header.i=ryantxu@gmail.com Received: from mr.google.com ([10.182.76.229]) by 10.182.76.229 with SMTP id n5mr1394882obw.14.1330110388909 (num_hops = 1); Fri, 24 Feb 2012 11:06:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=l3LLT3ZkyZaFt/XGc3Uzm21LyAJ+4GRX0Eu1Fp62g5A=; b=tr9Lj0iFofug4A+INXoFK+HU0PR3QIeU0TVYtkCqDd2EykQG/6u7v1Q4jXIyCFp1hi +eS8h1KPSrxI3Xmp4icnQ9BHYb9eeLy9wRoe+yItMwlM3L1cchkgcrBiYGomuCT2uKTk kI4RXKFmBGjoUhbpi+V2u02nbTvrZYahKxqTA= MIME-Version: 1.0 Received: by 10.182.76.229 with SMTP id n5mr1199825obw.14.1330110388842; Fri, 24 Feb 2012 11:06:28 -0800 (PST) Received: by 10.182.88.2 with HTTP; Fri, 24 Feb 2012 11:06:28 -0800 (PST) In-Reply-To: References: Date: Fri, 24 Feb 2012 11:06:28 -0800 Message-ID: Subject: Re: customization for SolrRequestParsers From: Ryan McKinley To: dev@lucene.apache.org Content-Type: multipart/alternative; boundary=f46d044785d53d2ee404b9ba7516 --f46d044785d53d2ee404b9ba7516 Content-Type: text/plain; charset=ISO-8859-1 I don't know exactly what you are trying to do... but you *may* be able to do it by overriding SolrDispatchFilter#execute(...) In my app, we add authentication tokens to the request context there. On Fri, Feb 24, 2012 at 7:49 AM, Mikhail Khludnev < mkhludnev@griddynamics.com> wrote: > Hello, > > I see that some sort of customization was expected for SolrRequestParsers. > http://svn.apache.org/viewvc/lucene/dev/trunk/solr/core/src/java/org/apache/solr/servlet/SolrRequestParsers.java?view=markup > > line > 97 // I don't see a need to have this publicly configured just yet > and > 111 // TODO -- in the future, we could pick a different parser based on > the request > > I need to plug some code which will parse request and add additional stuff > iinto req.context. I'd be happy to contribute it, but want to know what was > an intention. > > Thanks in advance > > -- > Sincerely yours > Mikhail Khludnev > Lucid Certified > Apache Lucene/Solr Developer > Grid Dynamics > > > > > --f46d044785d53d2ee404b9ba7516 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I don't know exactly what you are trying to do... but you *may* be able= to do it by overriding=A0SolrDispatchFilter#execute(...)

In my app, we add authentication tokens to the request context there.



On Fri, F= eb 24, 2012 at 7:49 AM, Mikhail Khludnev <mkhludnev@griddynamics.com>= wrote:
Hello,


line=A0
<= td style=3D"vertical-align:top;border-right-width:1px;background-color:rgb(= 238,238,238);color:rgb(80,80,80);text-align:right;border-right-style:solid;= border-right-color:rgb(80,80,80);padding-top:1px;padding-right:5px;padding-= bottom:1px;padding-left:5px"> 97
// I don't see a need to have this publicly configured just yet
and=A0
<= td style=3D"vertical-align:top;border-right-width:1px;background-color:rgb(= 238,238,238);color:rgb(80,80,80);text-align:right;border-right-style:solid;= border-right-color:rgb(80,80,80);padding-top:1px;padding-right:5px;padding-= bottom:1px;padding-left:5px"> 111
// TODO -- in the future, we could pick a different parser based on the= request

I need = to plug some code which will parse request and add additional stuff iinto r= eq.context. I'd be happy to contribute it, but want to know what was an= intention.=A0

Thanks in advance

--
Sincerely yours
Mikhail KhludnevLucid Certified
Apache Lucene/Solr Developer
Grid Dynamics




--f46d044785d53d2ee404b9ba7516--