Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 36442 invoked from network); 29 Mar 2011 14:15:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Mar 2011 14:15:26 -0000 Received: (qmail 7503 invoked by uid 500); 29 Mar 2011 14:15:25 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 7456 invoked by uid 500); 29 Mar 2011 14:15:25 -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 7448 invoked by uid 99); 29 Mar 2011 14:15:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 14:15:25 +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 (nike.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 14:15:18 +0000 Received: by fxm7 with SMTP id 7so331287fxm.35 for ; Tue, 29 Mar 2011 07:14:58 -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; bh=7jksY9sWKLhn67fvvqzs3eP6zIW91Sx7BZOQetOVMQw=; b=hpJngy6osKG6XoYLHcWGNDuVTDnmQM4rFUywIwm9cuw8khb8W1V4cDWuM9mJlmRBk7 NH5OHhgGGkClUjXFjdg8aGi6XOMTmGU2BgPZ4vMvetmmqfMDCZHKf6idnbX6sb+9MSij tJSYg5Q7hE/g36MPj5nQWksiu81s0PCdYVylY= 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; b=w6PQaK6mmd9+7W2+QvpuxIdmXylCfiV3GprsFumHSAgNHGeTkXoO3BllNChNvX7SJX UHKpF8N6UpZ+vSISW2me59FXt5X/sZJLwkrOJW4dDFo1KvnIKoAeMqSR+v2twWrNHYIy DBPt/9Tr1pFLH2cyXnIAHZLIH6bmAGPwEiF04= MIME-Version: 1.0 Received: by 10.223.125.196 with SMTP id z4mr620779far.28.1301408098335; Tue, 29 Mar 2011 07:14:58 -0700 (PDT) Sender: yseeley@gmail.com Reply-To: yonik@lucidimagination.com Received: by 10.223.111.79 with HTTP; Tue, 29 Mar 2011 07:14:58 -0700 (PDT) In-Reply-To: References: <549361831.13318.1301113506431.JavaMail.tomcat@hel.zones.apache.org> Date: Tue, 29 Mar 2011 10:14:58 -0400 X-Google-Sender-Auth: OKWhGtYDpn1TvSXHxi9asJvNdUM 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 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Mar 29, 2011 at 10:08 AM, Ryan McKinley wrote: >>> >>> 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. >>> >> >> The use cases I can think of are either very simple or very complex. >> I like this because it lets simple happen inline, and complex can >> happen in Components/Handlers/elsewhere >> > > Another key example would be inline highlighting: > > &id,_hl:title_,body If we're going to come up with another syntax, it needs to be fully fleshed out. This one already looks ambiguous in the context of "fl". For example, does that mean give me "id","title highlighted","body" or does it mean "id","title and body highlighted"? -Yonik http://www.lucenerevolution.org -- Lucene/Solr User Conference, May 25-26, San Francisco --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org