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 4859C17A14 for ; Wed, 4 Mar 2015 16:33:57 +0000 (UTC) Received: (qmail 12357 invoked by uid 500); 4 Mar 2015 16:33:52 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 12288 invoked by uid 500); 4 Mar 2015 16:33:52 -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 12276 invoked by uid 99); 4 Mar 2015 16:33:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2015 16:33:51 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of darincs@gmail.com designates 209.85.216.43 as permitted sender) Received: from [209.85.216.43] (HELO mail-qa0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2015 16:33:24 +0000 Received: by mail-qa0-f43.google.com with SMTP id bm13so34597676qab.2 for ; Wed, 04 Mar 2015 08:33:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=09v1ympaltoQ2tzKx3RHvekc1q5LQX62evjp21JORqI=; b=ADdiVCf5eM6uxewyxFe+2R4bLfmz77c/LfxxshTRsuLY8gdmk4WjTpFNG4gP4OQjyD +tuwuyeGoOli36XlseKimsyqWFCy9bCaRqujIQWhQ9TlAsbpRHnv+VHdOWS6VcFRzoCg F8b5QyS9aeHsoCb1ZjlpinhiWndWnPbJdPvlXvDcmSPaC5OZQJKeoU+HrYiJQiyVPpPt GzJTu3R7RYF0OKRBBoiF5iQHqMJ9sPH7vdwvFU6k08mPDxrqIu/M7hCW1njaUTRme/Gl nNZvOhpl1t4KtawGgY2BpzxmrQccFKuE2M7VIlNiEluyROw7UB2v374/NqE6x/WRJTGD 5GRg== X-Received: by 10.55.40.19 with SMTP id o19mr8739110qkh.90.1425486802885; Wed, 04 Mar 2015 08:33:22 -0800 (PST) Received: from [10.1.217.11] ([65.210.129.209]) by mx.google.com with ESMTPSA id b64sm1334244qkh.36.2015.03.04.08.33.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Mar 2015 08:33:21 -0800 (PST) From: Darin Amos Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Multivalu field grouping Message-Id: <46A037BB-91F3-4ED5-B28B-F6A8554958B6@gmail.com> Date: Wed, 4 Mar 2015 11:33:22 -0500 To: solr-user@lucene.apache.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-Virus-Checked: Checked by ClamAV on apache.org Hi All, I sent an email out earlier but I didn=E2=80=99t get any responses so I = thought I would try to reframe the question.=20 I have a problem that I believe multivalued field grouping is the = perfect answer for, of course since SOLR doesn=E2=80=99t support = multivalued field grouping, I need to find an alternate approach. Or = perhaps someone has found a way to do multivalue field grouping. My client is an ecommerce firm and lets says they have a category page = Where they want to show ALL shirts, but the results are grouped by a = subcategory, tee-shirt, sweater, tec.... If he subcategory is a single = value field this works fine, but a product document could belong to = multiple categories. Perhaps there is a =E2=80=9CPopular=E2=80=9D or = =E2=80=9CTrendy=E2=80=9D category that a production would also belong = to. My gut tells me this is a perfect fit for grouping on multi valued = fields, and I can=E2=80=99t think of another way to solve this easily = without finding a completely new way to index. Thanks! Darin *PS: For example, I would want my results returned like the below = (simplified): All Shirts: - Trendy - Tee Shirt 1 - Tee Shirt 2 - Sweater 1 - Sweater 2 - Tee Shirts - Tee Shirt 1 - Tee Shirt 2 - Tee Shirt 3 - Tee Shirt 4 - Sweaters - Sweater 1 - Sweater 2 - Sweater 3 - Sweater 4