if i'm understanding you: you're really just suggesting a syntactic
change, correct? true becomes count and false becomes lex ?
Yes. For now, it would be just that. In the future I guess there'll probably be
more ways to sort.
(the slightly tricky thing is making it a string param but
: The redesign I propose is changing the facet.sort parameter from a boolean to
a
: string and explicitely specify the sort method (with a default method if the
: parameter isn't specified). You'd use facet.sort=count to sort by facet count
: and something like facet.sort=lex to sort
Hi all,
I've been thinking about redesigning the facet.sort parameter (mostly because
of the issues arising from SOLR-764). I'll briefly outline my concerns.
- facet.sort=false and facet.sort=true don't do what one would intuitively think
they do -- both return the facets sorted, just how
PROTECTED]
To: solr-dev@lucene.apache.org
Sent: Friday, September 19, 2008 7:41:55 AM
Subject: facet.sort parameter
Hi all,
I've been thinking about redesigning the facet.sort parameter (mostly because
of the issues arising from SOLR-764). I'll briefly outline my concerns.
- facet.sort=false
Changing the facet.sort parameter to a string will be
backwards-incompatible. Do we have any other option?
Well the other option is to keep everything as it is now, which I'm sort of
opposed to because of the reasons outlined in my previous email. We could build
in some form of backward
