: Faceting on manufacturers and categories first and than present the
: corresponding facets might be used under some circumstances, but in my case
: the category structure is quite deep, detailed and complex. So when
: the user enters a query I like to say to him Look, here are the
:
On Tue, 2007-06-19 at 11:09 -0700, Chris Hostetter wrote:
I solve this problem by having metadata stored in my index which tells
my custom request handler what fields to facet on for each category ...
How do you define this metadata?
Cheers,
Martin
but i've also got several thousand
On Tue, 2007-06-19 at 19:16 +0200, Thomas Traeger wrote:
Hi,
I'm also just at that point where I think I need a wildcard facet.field
parameter (or someone points out another solution for my problem...).
Here is my situation:
I have many products of different types with totally different
Martin Grotzke schrieb:
On Tue, 2007-06-19 at 19:16 +0200, Thomas Traeger wrote:
Hi,
I'm also just at that point where I think I need a wildcard facet.field
parameter (or someone points out another solution for my problem...).
Here is my situation:
I have many products of different
On Wed, 2007-06-20 at 12:59 +0200, Thomas Traeger wrote:
Martin Grotzke schrieb:
On Tue, 2007-06-19 at 19:16 +0200, Thomas Traeger wrote:
[...]
I think it would be really nice, if I don't have to know which facets
fields are there at query time, instead just import attributes into
: to make it clear, i agree that it doesn't make sense faceting on all
: available fields, I only want faceting on those 300 attributes that are
: stored together with the fields for full text searches. A
: product/document has typically only 5-10 attributes.
:
: I like to decide at index time
Chris Hostetter schrieb:
: to make it clear, i agree that it doesn't make sense faceting on all
: available fields, I only want faceting on those 300 attributes that are
: stored together with the fields for full text searches. A
: product/document has typically only 5-10 attributes.
:
: I like
On Wed, 2007-06-20 at 12:49 -0700, Chris Hostetter wrote:
: I solve this problem by having metadata stored in my index which tells
: my custom request handler what fields to facet on for each category ...
: How do you define this metadata?
this might be a good place to start, note that
: I realized, that the facets are build out of the whole index, not the
: subset
: returned by the initial query. Therefore I have a large number of empty
: facets which I simply ignore. In my case the QueryTime is somewhat
facet.mincount is a way to tell solr not to bother giving you those 0
On 6/20/07, Chris Hostetter [EMAIL PROTECTED] wrote:
facet.mincount is a way to tell solr not to bother giving you those 0
counts ...
An aside: shouldn't that be the default? All of the people using
facets that I have seen always have to set facet.mincount=1 (or
facet.zeros=false)
-Yonik
Hi,
I'm also just at that point where I think I need a wildcard facet.field
parameter (or someone points out another solution for my problem...).
Here is my situation:
I have many products of different types with totally different
attributes. There are currently more than 300 attributes
: I have many products of different types with totally different
: attributes. There are currently more than 300 attributes
: I use dynamic fields to import the attributes into solr without having
: to define a specific field for each attribute. Now when I make a query I
: would like to get
Thanks for a great project.
Is it possible to request all facet.fields for a given facet.query instead
of having to request specific facet.fields? e.g. is there a wildcard for
facet.fields?
--
James.
http://blog.floehopper.org
On 6/18/07, James Mead [EMAIL PROTECTED] wrote:
Is it possible to request all facet.fields for a given facet.query instead
of having to request specific facet.fields? e.g. is there a wildcard for
facet.fields?
Not currently.
Can you elaborate on the problem you are trying to solve? Are you
14 matches
Mail list logo
