Re: To truncate or not to truncate (group.truncate vs. facet)

[rasser]

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: 
http://lucene.472066.n3.nabble.com/To-truncate-or-not-to-truncate-group-truncate-vs-facet-tp3838797p3840350.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: To truncate or not to truncate (group.truncate vs. facet)

[rasser]

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 to
combine faceting on both product and variant fields

Thanks



--
View this message in context: 
http://lucene.472066.n3.nabble.com/To-truncate-or-not-to-truncate-group-truncate-vs-facet-tp3838797p3840362.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: To truncate or not to truncate (group.truncate vs. facet)

[rasser]

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 year". How could this be handled with the above approach?

Thanks

--
View this message in context: 
http://lucene.472066.n3.nabble.com/To-truncate-or-not-to-truncate-group-truncate-vs-facet-tp3838797p3840406.html
Sent from the Solr - User mailing list archive at Nabble.com.

SV: To truncate or not to truncate (group.truncate vs. facet)

[rasser]

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:


Audi A4
audi
A4_black
black
white


Audi A4
audi
A4_white
white


Volvo V50
volvo
Volvo_V50
black


Audi A5
audi
A5_white
white


Audi S8
audi
S8_yellow
yellow


Audi S8
audi
S8_black
black
white


My goal is to to get this facet:
brand
-
audi (3)  -> since there are 3 audi models (A4,A5 and S8)
volvo (1) -> since there is only one volvo model (V50)

color
-
black (3) -> since all models except except A5 is available in black
white (3) -> since A4,A5 and S8 is available in white
yellow (1) -> since only S8 is available in yellow

Thanks


Fra: Erick Erickson [via Lucene] [ml-node+s472066n3842071...@n3.nabble.com]
Sendt: 20. marts 2012 12:42
Til: Rasmus Østergård
Emne: Re: To truncate or not to truncate (group.truncate vs. facet)

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 be to forget about grouping
and just facet. Then have your application change the counts
for all the "brand" entries to 1.

Best
Erick

On Mon, Mar 19, 2012 at 5:23 PM, rasser <[hidden email]> 
wrote:

> 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 year". How could this be handled with the above approach?
>
> Thanks
>
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/To-truncate-or-not-to-truncate-group-truncate-vs-facet-tp3838797p3840406.html
> Sent from the Solr - User mailing list archive at Nabble.com.



If you reply to this email, your message will be added to the discussion below:
http://lucene.472066.n3.nabble.com/To-truncate-or-not-to-truncate-group-truncate-vs-facet-tp3838797p3842071.html
To unsubscribe from To truncate or not to truncate (group.truncate vs. facet), 
click 
here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3838797&code=cm9zQHZlcnRpY2EuZGt8MzgzODc5N3wxOTg1NDU0NDUx>.
NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>


--
View this message in context: 
http://lucene.472066.n3.nabble.com/SV-To-truncate-or-not-to-truncate-group-truncate-vs-facet-tp3843321p3843321.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: To truncate or not to truncate (group.truncate vs. facet)

[rasser]

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:


Audi A4
audi
A4_black
black
white


Audi A4
audi
A4_white
white


Volvo V50
volvo
Volvo_V50
black


Audi A5
audi
A5_white
white


Audi S8
audi
S8_yellow
yellow


Audi S8
audi
S8_black
black
white


My goal is to to get this facet: 
brand 
- 
audi (3)  -> since there are 3 audi models (A4,A5 and S8)
volvo (1) -> since there is only one volvo model (V50)

color 
- 
black (3) -> since all models except except A5 is available in black
white (3) -> since A4,A5 and S8 is available in white
yellow (1) -> since only S8 is available in yellow 

And these 4 results (when query is *:*)

- Audi A4
- Audi A5
- Audi S8
- Volvo V50


Thanks

--
View this message in context: 
http://lucene.472066.n3.nabble.com/To-truncate-or-not-to-truncate-group-truncate-vs-facet-tp3838797p3843596.html
Sent from the Solr - User mailing list archive at Nabble.com.