: danjfoley [mailto:d...@micamedia.com]
Sent: Monday, April 09, 2012 7:26 PM
To: solr-user@lucene.apache.org
Subject: Re: To truncate or not to truncate (group.truncate vs. facet)
Is this planned as a future feature? Is it in the bug tracker as a feature
yet..just wondering how long until
: Monday, April 09, 2012 7:26 PM
To: [hidden email] http://user/SendEmail.jtp?type=nodenode=3900432i=1
Subject: Re: To truncate or not to truncate (group.truncate vs. facet)
Is this planned as a future feature? Is it in the bug tracker as a feature
yet..just wondering how long until
[mailto:d...@micamedia.com]
Sent: Saturday, April 07, 2012 7:02 PM
To: solr-user@lucene.apache.org
Subject: Re: To truncate or not to truncate (group.truncate vs. facet)
I've been searching for a solution to my issue, and this seems to come closest
to it. But not exactly.
I am indexing clothing
-Original Message-
From: danjfoley [mailto:d...@micamedia.com]
Sent: Saturday, April 07, 2012 7:02 PM
To: solr-user@lucene.apache.org
Subject: Re: To truncate or not to truncate (group.truncate vs. facet)
I've been searching for a solution to my issue, and this seems to come closest
You tried adding the parameter
group.facet=true ?
Cody
-Original Message-
From: danjfoley [mailto:d...@micamedia.com]
Sent: Monday, April 09, 2012 10:09 AM
To: solr-user@lucene.apache.org
Subject: Re: To truncate or not to truncate (group.truncate vs. facet)
I did get this working
, 2012 10:36 AM
To: solr-user@lucene.apache.org
Subject: RE: To truncate or not to truncate (group.truncate vs. facet)
You tried adding the parameter
group.facet=true ?
Cody
-Original Message-
From: danjfoley [mailto:d...@micamedia.com]
Sent: Monday, April 09, 2012 10:09 AM
To: solr-user
[mailto:cody.yo...@move.com]
Sent: Monday, April 09, 2012 10:36 AM
To: solr-user@lucene.apache.org
Subject: RE: To truncate or not to truncate (group.truncate vs. facet)
You tried adding the parameter
group.facet=true ?
Cody
-Original Message-
From: danjfoley [mailto:d...@micamedia.com]
Sent: Monday
, Cody [mailto:cody.yo...@move.com]
Sent: Monday, April 09, 2012 10:36 AM
To: solr-user@lucene.apache.org
Subject: RE: To truncate or not to truncate (group.truncate vs. facet)
You tried adding the parameter
group.facet=true ?
Cody
-Original Message-
From: danjfoley [mailto:d
(group.truncate vs. facet)
You tried adding the parameter
group.facet=true ?
Cody
-Original Message-
From: danjfoley [mailto:d...@micamedia.com]
Sent: Monday, April 09, 2012 10:09 AM
To: solr-user@lucene.apache.org
Subject: Re: To truncate or not to truncate (group.truncate vs. facet)
I
I've been searching for a solution to my issue, and this seems to come
closest to it. But not exactly.
I am indexing clothing. Each article of clothing comes in many sizes and
colors, and can belong to any number of categories.
For example take the following: I add 6 documents to solr as
Faceting is orthogonal to grouping, so be careful what you
ask for. So adding faceting would be easy, the only reason
I suggested grouping is your requirement that your brands be
just a count of the number of distinct ones found, not the
number of matching docs.
So a really simple solution would
Thanks for taking the time to help me Erick!
Just to clarify my desired behavior from the facets. This is the index,
notice color is multivalued to represent a model of car that has more than
one color:
doc
field name=skuAudi A4/field
field name=brandaudi/field
field
Ok, assuming sku is an un-tokenized field (and if it isn't, use
a copyField) then just facet on that field. Then, at the app layer,
combine them to get your aggregate counts.
So your raw return would have
Audi A4 (2)
Audi A5 (1)
Audi S8 (2)
Volvo V50 (1)
The app would have to be smart enough to
Groups and faceting are orthogonal and really have nothing to do with
each other, so that might be where part of the problem lies.
In your example, you can consider grouping by brand and count the
*groups* returned, not elements within those groups. Then you're
simply counting up the groups
Hi Rasmus,
You might want to use the group.facet parameter:
http://wiki.apache.org/solr/FieldCollapsing#Request_Parameters
I think that will give you the right facet counts with faceting. The
parameter is not available in Solr 3.x, so you'll need to use a 4.0 nightly
build.
Martijn
On 19 March
Thanks for your reply Erick,
As far as I can see grouping on brand (group.field=brand) will only work if
all rows are returned. Correct?
- if this is so it will not fly since only the top results are returned
(rows=100)
Or am I missing something.
Thanks
--
View this message in context:
Thanks for the suggestion Martijn.
I did see that v. 4 had a group.facet parameter that seems to fit my needs.
But since I'm new to Solr I'm not really comfortable using version 4 in
production, let alone a nightly build.
Any other ideas? - I cant imagine that i'm the first person ever trying
Well, it depends on how many groups we're talking here. Grouping
returns the top N results _within_ each group. So if you have 10
brands and grouped on brand, you'd get back the top, say, 3 results
for Ford, Volvo, Fiat, Saab, Audi.up to 10 groups.
The number of groups you get back is
I see your point.
If I understand it correct it will however mean that i need to return
10(brands)x100(resultToShow) = 1000 docs to facilitate that all 100 results
to show is of the same brand. Correnct?
And tomorrow (or later) the customer will also want a facet on 5 new fields
eg. production
19 matches
Mail list logo
