Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E303D799 for ; Fri, 7 Sep 2012 14:26:54 +0000 (UTC) Received: (qmail 90403 invoked by uid 500); 7 Sep 2012 14:26:50 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 90329 invoked by uid 500); 7 Sep 2012 14:26:50 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 90320 invoked by uid 99); 7 Sep 2012 14:26:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Sep 2012 14:26:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dotancohen@gmail.com designates 209.85.161.176 as permitted sender) Received: from [209.85.161.176] (HELO mail-gg0-f176.google.com) (209.85.161.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Sep 2012 14:26:44 +0000 Received: by ggke5 with SMTP id e5so607399ggk.35 for ; Fri, 07 Sep 2012 07:26:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=xAlU8z6WESWl41xo7fmxL8W+T6ziO/N9gEOtA9iY78g=; b=jBNB9BvqGtlnlEa7p3iyuVCv1iDhpVPNvl5W8V1fK9hwNdqnmJIkFqsAmysACHvFXf wqyWO10kWuiKCWxrHU5RNWA7CA+3RAmpVgMnJBcQ0lNmcGy2jqxDTdZM6892HtO3L09n UGcp+g7/zxAjAGbj0QM0E14c6WmMP76+nAZhB/14ZPVGFIZUQ0YueNqI5pOFnDGklbYA uZ7iFgHE1UFP2b62Gzn4Bsyfpp2qLj0c6s7XKV8XYBlCH7jbJEvaJYVJCsfeR8eitoh6 JZ/b4aL/MKjP3fbRkUYvzCmNja3XNgmwrb7J2408qeNsIwx9LXF0v1bjqjxEu5927KVx lAgA== MIME-Version: 1.0 Received: by 10.58.33.234 with SMTP id u10mr7934973vei.49.1347027984094; Fri, 07 Sep 2012 07:26:24 -0700 (PDT) Received: by 10.58.94.19 with HTTP; Fri, 7 Sep 2012 07:26:24 -0700 (PDT) In-Reply-To: <51437164-7835-4B1B-A660-5EE1C3ECEADD@gmail.com> References: <0D044544-7B96-4100-B567-D5D2812C43CA@gmail.com> <055C1BA8-4A5D-4BED-BEF1-F869B7D7BA47@gmail.com> <51437164-7835-4B1B-A660-5EE1C3ECEADD@gmail.com> Date: Fri, 7 Sep 2012 17:26:24 +0300 Message-ID: Subject: Re: Unexpected results in Solr 4 Pivot Faceting From: Dotan Cohen To: solr-user@lucene.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Sep 7, 2012 at 4:39 PM, Erik Hatcher wrote= : >> Just to be clear, as I'm not logged onto the dev server at the moment >> but it was implied in an earlier mail: Any field that is to be pivoted >> on needs to be a string field? Is that documented, as I cannot find >> that in the docs. > > No, it doesn't need to be a string field.... but whatever terms come out = of the analysis process are what gets faceted upon. If it was a "text" fie= ld, each word in the field would be a facet value. A "trie" field probably= doesn't work properly, as it indexes multiple terms per value and you'd ge= t odd values. Pivot faceting was initially implemented only with textual = terms in mind, and string is generally the desired type. > Thanks for the insight. I'll see how much time for experimentation I might afford. --=20 Dotan Cohen http://gibberish.co.il http://what-is-what.com