Hmmm ... it went a long way than I thought :) i think Avlesh is just suggesting that... > facet.field=foo & f.foo.facet.prefix=a & f.foo.facet.prefix=z > You are absolutely right, Hoss.
Until Yonik mentioned the "sort" behavior of facets, it never came into my mind. My SQL analogy was .. "select ... where facet_field like "foo_%" or facet_field like "bar_%" order by facetCount". Ordering between these was something that I did not naturally desire. Its a nice to have thing for sure. Should I create a Jira issue for this enhancement? Cheers Avlesh On Fri, Aug 21, 2009 at 11:04 AM, Chris Hostetter <[email protected]>wrote: > > : Ah, yeah... in this case the client would be able to determine which > : was which by the prefix of the label. But it brings up interesting > : points about ordering... should all of prefix "A" come before prefix > : "B" or should they be sorted by frequency. If it's the latter case, > > i don't see why the facet.sort param wouldn't dictate that, just like i > would expect facet.limit to keep working. > > : then it seems like it's more the case of wanting an additional filter > : applied to the facet, which we should also support at some point. > > it's just a simple matter of programming ... and hard matter of finding > the time/energy. > > > > -Hoss > >
