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 > >> dynamic fields, get the relevant facets back and decide in the frontend > >> which to display and how... > >> > > Do you really need all facets in the frontend? > > > no, only the subset with matches for the current query. ok, that's somehow similar to our requirement, but we want to get only e.g. the first 5 relevant facets back from solr and not handle this in the frontend.
> > Would it be a solution to have a facet ranking in the field definitions, > > and then decide at query time, on which fields to facet on? This would > > need an additional query parameter like facet.query.count. [...] > > > One step after the other ;o), the ranking of the facets will be another > problem I have to solve, counts of facets and matching documents will be > a starting point. Another idea is to use the score of the documents > returned by the query to compute a score for the facet.field... Yep, this is also different for different applications. I'm also interested in this problem and would like to help solving this problem (though I'm really new to lucene and solr)... Cheers, Martin > > Tom > -- Martin Grotzke http://www.javakaffee.de/blog/
signature.asc
Description: This is a digitally signed message part
