Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 9347 invoked from network); 21 Aug 2009 02:19:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Aug 2009 02:19:42 -0000 Received: (qmail 42156 invoked by uid 500); 21 Aug 2009 02:20:00 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 42094 invoked by uid 500); 21 Aug 2009 02:20:00 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 42084 invoked by uid 99); 21 Aug 2009 02:20:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2009 02:20:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yseeley@gmail.com designates 209.85.220.225 as permitted sender) Received: from [209.85.220.225] (HELO mail-fx0-f225.google.com) (209.85.220.225) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2009 02:19:37 +0000 Received: by fxm25 with SMTP id 25so256597fxm.5 for ; Thu, 20 Aug 2009 19:19:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=crzXpVBpn70iQL/IjWSfBxoL/oPe1bFIkLkcqFcplZg=; b=kV3x7hw59PtiEaejdc8vs6is7DTz0OQg3RO4HbJUfSGQ2BCfs26yMWoTiYXCCOloHU FQH9VEVwV2hShFMdfIJqZtIQRGvFMPGlTTa3sQMtZTpCuAjFzKqCByDgdpTm1NOV3AyH 1wy/tL4QMrToowuq0EWg0LiBDh+xwdv2G/5bk= 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=U/eV1fJ2TcZh2WoQnhtZWBQhuaL/oQ0B/FmUNlydHOboo49f1clLUR2tDR15mlbqPF Nd2kPzDDSFk+zoevxaVEKfzUSj+SzRWVLX2qZGBfh3SYr43k85Jfwuh8+KkvKWJpSo+K kYnRp2fagnRmSq6cmpXcZk//uochWbzuL58D8= MIME-Version: 1.0 Received: by 10.223.54.15 with SMTP id o15mr106817fag.96.1250821157471; Thu, 20 Aug 2009 19:19:17 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Aug 2009 22:19:17 -0400 Message-ID: Subject: Re: Multiple facet.prefix? From: Yonik Seeley To: solr-dev@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Aug 20, 2009 at 10:13 PM, Avlesh Singh wrote: > Or, may be just multiple facet.prefix values, Yonik; exactly the same as > facet.field works. The problem then becomes labels. facet.field=foo goes under the label "foo" We already have a mechanism to re-label results, seems like we should use that? -Yonik http://www.lucidimagination.com > Cheers > Avlesh > > On Fri, Aug 21, 2009 at 7:39 AM, Yonik Seeley wrote: > >> On Thu, Aug 20, 2009 at 9:53 PM, Avlesh Singh wrote: >> > Should multiple values for facet.prefix be supported? >> > I have come across several use-cases on the user mailing list where such >> a >> > functionality could have helped (The latest one being - >> > >> http://www.lucidimagination.com/search/document/2a9c44d4f015b5e5/facet_filtering >> ). >> > I ran into one such use last night. >> > >> > Is there a general agreement on the enhancement? >> >> Yes, I think it's a good idea. >> It's just that the current syntax doesn't quite support it yet. >> >> I think that once again, local params are the answer... the same as >> they were with faceting on a single field but excluding different >> filters. >> >> facet.field={!prefix=foo key=label1}myfield >> facet.field={!prefix=bar key=label2}myfield >> >> -Yonik >> http://www.lucidimagination.com >> >