that's a very slippery slop .. i suspect a lot of users would be put-off
by ranges that kept changing on them as they added/removed other facet
constraints -- one minute you are seeing ranges like 0-10,11-20,20-30 and
then you say you are only interested in red products and now your ranges
are 0-
: way but it would be nice to have different buckets depending on the result
: set that you have in the category
: vs.
: using the same buckets for any result set in a category even though they
: don't make as much sense anymore depending on the facets selected.
that's a very slippery slop .. i s
that's certianly one way to do it ... it would probably be faster though
to use the TermEnum of the price field directly.
I will look into this.
i've yet to really see a good appraoch to progomaticaly
determining (non-trivial) numeric ranges, personally i think that to have
good looking ran
: Let me back up.. for a second. I want to create price ranges. I was thinking
: that I would do a search with a sort on price and create ranges by getting
: the document price every (docCount / #ofpricerangesIwant). Basically create:
: < 10, 10 - 60, 60 - 100 etc.. If the initial search wasn't so
