Return-Path: 
 <dev-return-112308-apmail-lucene-dev-archive=lucene.apache.org@lucene.apache.org>
X-Original-To: apmail-lucene-dev-archive@www.apache.org
Delivered-To: apmail-lucene-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2F941D477
	for <apmail-lucene-dev-archive@www.apache.org>;
 Mon, 22 Oct 2012 06:12:14 +0000 (UTC)
Received: (qmail 19032 invoked by uid 500); 22 Oct 2012 06:12:12 -0000
Delivered-To: apmail-lucene-dev-archive@lucene.apache.org
Received: (qmail 18951 invoked by uid 500); 22 Oct 2012 06:12:12 -0000
Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:dev@lucene.apache.org>
List-Id: <dev.lucene.apache.org>
Reply-To: dev@lucene.apache.org
Delivered-To: mailing list dev@lucene.apache.org
Received: (qmail 18931 invoked by uid 99); 22 Oct 2012 06:12:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 06:12:12 +0000
Date: Mon, 22 Oct 2012 06:12:11 +0000 (UTC)
From: "ZhengBowen (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <911747749.8517.1350886331930.JavaMail.jiratomcat@arcas>
In-Reply-To: <2072960388.8484.1350884897953.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (SOLR-3973) Cross facet
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/SOLR-3973?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

ZhengBowen updated SOLR-3973:
-----------------------------

    Description:=20
We often come across the scene of the multi-faceted cross, For example, the=
 SQL statement, select count( * ) from table group by A,B.=20

Now we slightly modified for FacetComponent, this component to be able to s=
upport the multi-faceted cross.

Request parameters are as follows=EF=BC=9A
&start=3D0&rows=3D0&q=3D*:*&facet=3Dtrue&facet.field=3Duser_city&facet.fiel=
d=3Duser_province&facet.limit=3D10&facet.cross=3Dtrue&facet.cross.sep=3D,

The original effect is as follows:
<result name=3D"response" numFound=3D"479140" start=3D"0" sum=3D"0.0" max=
=3D"-Infinity" min=3D"Infinity"/>
<lst name=3D"facet_counts">
<lst name=3D"facet_queries"/>
<lst name=3D"facet_fields">
<lst name=3D"user_city">
<int name=3D"Beijing">16852</int>
<int name=3D"ShangHai">16787</int>
<int name=3D"Gunagzhou">12950</int>
<int name=3D"Shenzhen">11667</int>
<int name=3D"Hangzhou">9997</int>
<int name=3D"Chongqing">7624</int>
<int name=3D"Chengdu">7082</int>
<int name=3D"Wuhan">6894</int>
<int name=3D"Suzhou">6528</int>
<int name=3D"Tianjin">5822</int>
</lst>
<lst name=3D"user_province">
<int name=3D"Gunagdong">48621</int>
<int name=3D"Zhengjiang">34634</int>
<int name=3D"Jiangsu">28748</int>
<int name=3D"Shandong">20389</int>
<int name=3D"Fujian">18508</int>
<int name=3D"Beijing">16852</int>
<int name=3D"Shanghai">16787</int>
<int name=3D"Hubei">15227</int>
<int name=3D"Sichuan">15112</int>
<int name=3D"Hebei">13793</int>
</lst>
</lst>
<lst name=3D"facet_numTerms"/>
<lst name=3D"facet_dates"/>
<lst name=3D"facet_ranges"/>
</lst>

The effect of the new features are as follows=EF=BC=9A

<result name=3D"response" numFound=3D"479140" start=3D"0" sum=3D"0.0" max=
=3D"-Infinity" min=3D"Infinity"/>
<lst name=3D"facet_counts">
<lst name=3D"facet_queries"/>
<lst name=3D"facet_fields">
  <lst name=3D"user_city,user_province">
  <int name=3D"Beijing,Beijing">16852</int>
  <int name=3D"Shanghai,Shanghai">16787</int>
  <int name=3D"Guangzhou,Gunagdong">12950</int>
  <int name=3D"Shenzheng,Guangdong">11667</int>
  <int name=3D"Hangzhou,Zhejiang">9997</int>
  <int name=3D"Chongqing,Chongqing">7624</int>
  <int name=3D"Chengdu,Sichuan">7082</int>
  <int name=3D"Wuhan,Hubei">6894</int>
  <int name=3D"Suzhou,Jiangsu">6528</int>
</lst>
</lst>
<lst name=3D"facet_numTerms"/>
<lst name=3D"facet_dates"/>
<lst name=3D"facet_ranges"/>
</lst>
</response>

  was:
We often come across the scene of the multi-faceted cross, For example, the=
 SQL statement, select count( * ) from table1 group by A,B.=20

Now we slightly modified for FacetComponent, this component to be able to s=
upport the multi-faceted cross.

Request parameters are as follows=EF=BC=9A
&start=3D0&rows=3D0&q=3D*:*&facet=3Dtrue&facet.field=3Duser_city&facet.fiel=
d=3Duser_province&facet.limit=3D10&facet.cross=3Dtrue&facet.cross.sep=3D,

The original effect is as follows:
<result name=3D"response" numFound=3D"479140" start=3D"0" sum=3D"0.0" max=
=3D"-Infinity" min=3D"Infinity"/>
<lst name=3D"facet_counts">
<lst name=3D"facet_queries"/>
<lst name=3D"facet_fields">
<lst name=3D"user_city">
<int name=3D"Beijing">16852</int>
<int name=3D"ShangHai">16787</int>
<int name=3D"Gunagzhou">12950</int>
<int name=3D"Shenzhen">11667</int>
<int name=3D"Hangzhou">9997</int>
<int name=3D"Chongqing">7624</int>
<int name=3D"Chengdu">7082</int>
<int name=3D"Wuhan">6894</int>
<int name=3D"Suzhou">6528</int>
<int name=3D"Tianjin">5822</int>
</lst>
<lst name=3D"user_province">
<int name=3D"Gunagdong">48621</int>
<int name=3D"Zhengjiang">34634</int>
<int name=3D"Jiangsu">28748</int>
<int name=3D"Shandong">20389</int>
<int name=3D"Fujian">18508</int>
<int name=3D"Beijing">16852</int>
<int name=3D"Shanghai">16787</int>
<int name=3D"Hubei">15227</int>
<int name=3D"Sichuan">15112</int>
<int name=3D"Hebei">13793</int>
</lst>
</lst>
<lst name=3D"facet_numTerms"/>
<lst name=3D"facet_dates"/>
<lst name=3D"facet_ranges"/>
</lst>

The effect of the new features are as follows=EF=BC=9A

<result name=3D"response" numFound=3D"479140" start=3D"0" sum=3D"0.0" max=
=3D"-Infinity" min=3D"Infinity"/>
<lst name=3D"facet_counts">
<lst name=3D"facet_queries"/>
<lst name=3D"facet_fields">
  <lst name=3D"user_city,user_province">
  <int name=3D"Beijing,Beijing">16852</int>
  <int name=3D"Shanghai,Shanghai">16787</int>
  <int name=3D"Guangzhou,Gunagdong">12950</int>
  <int name=3D"Shenzheng,Guangdong">11667</int>
  <int name=3D"Hangzhou,Zhejiang">9997</int>
  <int name=3D"Chongqing,Chongqing">7624</int>
  <int name=3D"Chengdu,Sichuan">7082</int>
  <int name=3D"Wuhan,Hubei">6894</int>
  <int name=3D"Suzhou,Jiangsu">6528</int>
</lst>
</lst>
<lst name=3D"facet_numTerms"/>
<lst name=3D"facet_dates"/>
<lst name=3D"facet_ranges"/>
</lst>
</response>

   =20
> Cross facet
> -----------
>
>                 Key: SOLR-3973
>                 URL: https://issues.apache.org/jira/browse/SOLR-3973
>             Project: Solr
>          Issue Type: Improvement
>          Components: SearchComponents - other
>    Affects Versions: 3.5
>            Reporter: ZhengBowen
>              Labels: cross, facet, solr
>             Fix For: 3.5
>
>         Attachments: crossfacet.patch
>
>
> We often come across the scene of the multi-faceted cross, For example, t=
he SQL statement, select count( * ) from table group by A,B.=20
> Now we slightly modified for FacetComponent, this component to be able to=
 support the multi-faceted cross.
> Request parameters are as follows=EF=BC=9A
> &start=3D0&rows=3D0&q=3D*:*&facet=3Dtrue&facet.field=3Duser_city&facet.fi=
eld=3Duser_province&facet.limit=3D10&facet.cross=3Dtrue&facet.cross.sep=3D,
> The original effect is as follows:
> <result name=3D"response" numFound=3D"479140" start=3D"0" sum=3D"0.0" max=
=3D"-Infinity" min=3D"Infinity"/>
> <lst name=3D"facet_counts">
> <lst name=3D"facet_queries"/>
> <lst name=3D"facet_fields">
> <lst name=3D"user_city">
> <int name=3D"Beijing">16852</int>
> <int name=3D"ShangHai">16787</int>
> <int name=3D"Gunagzhou">12950</int>
> <int name=3D"Shenzhen">11667</int>
> <int name=3D"Hangzhou">9997</int>
> <int name=3D"Chongqing">7624</int>
> <int name=3D"Chengdu">7082</int>
> <int name=3D"Wuhan">6894</int>
> <int name=3D"Suzhou">6528</int>
> <int name=3D"Tianjin">5822</int>
> </lst>
> <lst name=3D"user_province">
> <int name=3D"Gunagdong">48621</int>
> <int name=3D"Zhengjiang">34634</int>
> <int name=3D"Jiangsu">28748</int>
> <int name=3D"Shandong">20389</int>
> <int name=3D"Fujian">18508</int>
> <int name=3D"Beijing">16852</int>
> <int name=3D"Shanghai">16787</int>
> <int name=3D"Hubei">15227</int>
> <int name=3D"Sichuan">15112</int>
> <int name=3D"Hebei">13793</int>
> </lst>
> </lst>
> <lst name=3D"facet_numTerms"/>
> <lst name=3D"facet_dates"/>
> <lst name=3D"facet_ranges"/>
> </lst>
> The effect of the new features are as follows=EF=BC=9A
> <result name=3D"response" numFound=3D"479140" start=3D"0" sum=3D"0.0" max=
=3D"-Infinity" min=3D"Infinity"/>
> <lst name=3D"facet_counts">
> <lst name=3D"facet_queries"/>
> <lst name=3D"facet_fields">
>   <lst name=3D"user_city,user_province">
>   <int name=3D"Beijing,Beijing">16852</int>
>   <int name=3D"Shanghai,Shanghai">16787</int>
>   <int name=3D"Guangzhou,Gunagdong">12950</int>
>   <int name=3D"Shenzheng,Guangdong">11667</int>
>   <int name=3D"Hangzhou,Zhejiang">9997</int>
>   <int name=3D"Chongqing,Chongqing">7624</int>
>   <int name=3D"Chengdu,Sichuan">7082</int>
>   <int name=3D"Wuhan,Hubei">6894</int>
>   <int name=3D"Suzhou,Jiangsu">6528</int>
> </lst>
> </lst>
> <lst name=3D"facet_numTerms"/>
> <lst name=3D"facet_dates"/>
> <lst name=3D"facet_ranges"/>
> </lst>
> </response>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org