I'd think that facet.query would work for you, something like: &facet=true&facet.query=FareJanStandard:[price1 TO price2]&facet.query:fareJanStandard[price2 TO price3] You can string as many facet.query clauses as you want, across as many fields as you want, they're all independent and will get their own sections in the response.
Best Erick On Wed, Dec 1, 2010 at 4:55 AM, lee carroll <lee.a.carr...@googlemail.com>wrote: > Hi > > I've built a schema for a proof of concept and it is all working fairly > fine, niave maybe but fine. > However I think we might run into trouble in the future if we ever use > facets. > > The data models train destination city routes from a origin city: > Doc:City > Name: cityname [uniq key] > CityType: city type values [nine possible values so good for faceting] > ... [other city attricbutes which relate directy to the doc unique key] > all have limited vocab so good for faceting > FareJanStandard:cheapest standard fare in january(float value) > FareJanFirst:cheapest first class fare in january(float value) > FareFebStandard:cheapest standard fare in feb(float value) > FareFebFirst:cheapest first fare in feb(float value) > ..... etc > > The question is how would i best facet fare price? The desire is to return > > number of citys with jan prices in a set of ranges > etc > number of citys with first prices in a set of ranges > etc > > install is 1.4.1 running in weblogic > > Any ideas ? > > > > Lee C >
