Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 29028 invoked from network); 29 Mar 2011 11:37:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Mar 2011 11:37:22 -0000 Received: (qmail 34151 invoked by uid 500); 29 Mar 2011 11:37:20 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 34108 invoked by uid 500); 29 Mar 2011 11:37:20 -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 34101 invoked by uid 99); 29 Mar 2011 11:37:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 11:37:20 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates 209.85.161.48 as permitted sender) Received: from [209.85.161.48] (HELO mail-fx0-f48.google.com) (209.85.161.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 11:37:14 +0000 Received: by fxm7 with SMTP id 7so145577fxm.35 for ; Tue, 29 Mar 2011 04:36:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=ca3MPq+kzp8kVqJDpzmEqFMwAesTZqgoN/fxK87QP9s=; b=O095zZOEOPAYYXNdiRBNqZb+JmS3dcyow97yyez6i7X1+0NGArJrQchpfFhBrjCA7Q KAQ2js1pGnJWiXq2RD7YXn77IQHL24k7GQcRdM6B+i5E7dpvlWabGbMU2k9nYZmOmexH HfvUukJZNN0Tg7NF22wU3pBLgv6569Juu6ld4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=mteZFy77+UAxK4AdQPTHjnu1G4+8x0sfsFtJiLm1QCDF9INnMw5B99UlTGxlgHthpK nyNXPyX+kGrYv+OGsE68jWtPcZAQ6noQxIPnJre5PRXQ8mL+/40L7cHCdh1/13vMIKxh j4bL833VoLdTbyozuSSEWDkOcW7tfiIYHbaqU= MIME-Version: 1.0 Received: by 10.223.160.5 with SMTP id l5mr3714292fax.85.1301398613133; Tue, 29 Mar 2011 04:36:53 -0700 (PDT) Sender: yseeley@gmail.com Reply-To: yonik@lucidimagination.com Received: by 10.223.111.79 with HTTP; Tue, 29 Mar 2011 04:36:53 -0700 (PDT) In-Reply-To: References: <549361831.13318.1301113506431.JavaMail.tomcat@hel.zones.apache.org> Date: Tue, 29 Mar 2011 07:36:53 -0400 X-Google-Sender-Auth: GWOURQVYf4TeCRe0EBgz-eNsLF4 Message-ID: Subject: Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents From: Yonik Seeley To: dev@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, Mar 28, 2011 at 11:26 PM, Ryan McKinley wrote: >> >> And I'm still on the fence - _explain_ alone does not justify a whole >> new syntax IMO... so we may need more usecase examples to figure out >> what problem we're actually trying to solve. >> > > The key use case I am thinking of is an easy way to add a value to the > the response. =A0In SQL: > > SELECT name,'hello' FROM ... > > With this syntax you can now use: > > fl=3Dname,_value:hello_ > > The existing syntax is totally ridiculous: > > fl=3Dname,{!transformer name=3Dvalue value=3Dhello} That's not the existing syntax. Or I guess you were just brainstorming about what using the existing localParams syntax would look like if you tried to apply it to transformers? Or are you saying that localParams syntax is ridiculous and should be replaced by something different? > I see a real need to be able to pass a simple value to a transformer. > Explain is just one of many examples. I was trying to think up what other real use cases actually where... because that really does have a bearing on if a new syntax should be developed, and what that syntax should look like. -Yonik --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org